skills.rest
Tashima-Tarsh
Tashima-TarshCOMMUNITY
Explore all skills by this author →
Website𝕏@thenitishkrGitHub

fullstack-dev

Enforce DISHA fullstack implementation standards across frontend and backend codebases.

1|Updated Apr 8, 2026
Search Tags:#test coverage#fullstack#feature implementation#api client#typed schemas#disha#governed development
One-click install
npx skills add https://github.com/Tashima-Tarsh/Disha --skill fullstack-dev-tashima-tarsh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fullstack-dev
Source: https://github.com/Tashima-Tarsh/Disha/tree/main/.codex/skills/fullstack-dev
Command: npx skills add https://github.com/Tashima-Tarsh/Disha --skill fullstack-dev-tashima-tarsh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent, ungoverned fullstack implementation for DISHA product features, ensuring all frontend and backend work adheres to the platform's architectural standards, scope boundaries, and reliability requirements.

Core Features & Use Cases

  • Architectural Rule Enforcement: Guides developers to follow DISHA's core implementation rules, including keeping controllers thin, moving business logic to services, and using typed schemas for all requests and responses.
  • Scope Boundary Control: Restricts first-pass feature work to the active src/ and web/ production directories to prevent unintended changes to ungoverned codebase areas.
  • Test Coverage Mandate: Requires adding or updating tests for all user-facing behavior to maintain product reliability and compliance with DISHA's verification standards.
  • Use Case: When building a new DISHA mission submission feature, this Skill ensures the backend controller only handles request routing, all validation and processing logic lives in a dedicated service, the frontend uses a centralized client module for API calls instead of embedding fetch logic in components, and corresponding tests are added for both successful submission and error scenarios.

Quick Start

Use the fullstack-dev skill to implement a new DISHA feature that follows all product architectural rules, maintains proper scope boundaries, and includes required test coverage for user-facing behavior.

Frequently Asked Questions about fullstack-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce architectural rules for fullstack feature implementation across frontend and backend codebases?▼

Fullstack feature implementation architectural rules are enforced by keeping controllers thin, moving business logic to the service layer, and using typed schemas for all API requests and responses to maintain structural consistency.

How do I structure API calls in a frontend client instead of embedding fetch logic directly in components?▼

Frontend API calls should be structured through a centralized client module rather than embedding fetch logic directly within UI components, ensuring consistent request handling and typed schema validation across the active web directory.

What is the best way to maintain test coverage for user-facing behavior during fullstack development?▼

Test coverage for user-facing behavior is maintained by mandating that all new feature development includes or updates tests covering both successful operations and error scenarios to satisfy product verification standards.

Can I restrict fullstack development scope to only active production directories?▼

Yes, fullstack development scope is restricted to active production `src/` and `web/` directories, preventing unintended changes to ungoverned codebase areas during first-pass feature work.

Why does my fullstack feature implementation require typed schemas for requests and responses?▼

Typed schemas for requests and responses are required to enforce governed fullstack implementation standards, ensuring architectural consistency and reliable data validation across frontend and backend integration layers.

Do I need to move business logic to a service layer when building fullstack features?▼

Yes, business logic must be moved to a dedicated service layer while keeping controllers thin for request routing, ensuring proper separation of concerns across the backend codebase.

Related Skills

Explore More Software Engineering Skills→
fritzprixfritzprix
8

system-setup

Install and verify MCP runtime dependencies across Windows, Linux, and macOS.

Community
Intermediate
ydnikolaevydnikolaev
8

qa-lead

Plan and validate E2E, API, and UI tests with generated reports.

Community
Advanced
hendrax5hendrax5

phase-6-ui-integration

Implement frontend UI and integrate it with backend APIs.

Community
Intermediate
ogprotegeogprotege

repo-doc-auditor

Audit repository documentation against code and recent changes.

Community
Advanced