Full Stack Development Companion

When taking over an unfamiliar project, the first step is often identifying its tech stack and structure to work correctly. For full-stack developers, frequent context-switching between frontend and backend can be confusing, and teams may lack standardized project kickoff and process guidelines.

The Specific Problem & Solution

This skill addresses the problem of "project context identification and development process initiation." It functions as an entry-level companion, providing an automated mechanism for project type detection and workflow routing. The core idea is to scan key characteristic files in the project root, determine if the workspace is frontend, backend, or full-stack, and then automatically guide the developer into a predefined, standardized development sub-process. This reduces the cognitive load of manual configuration and context switching.

Core Capabilities and Workflow

The skill operates through several clear steps:

• Automatic Project Detection: It scans the current directory and applies a set of rules for judgment:

  • Frontend Project: Identified by the presence of vue or react dependencies in package.json, config files like vite.config.ts or next.config.*, or specific directory structures such as src/views/.
  • Backend Project: Identified by files like composer.json (PHP/Laravel), go.mod (Go/Gin), manage.py (Django), requirements.txt, or pom.xml, signifying PHP, Go, Python, Java stacks, etc.
  • Full-Stack Project: Determined when both frontend and backend characteristics are matched.

• Intelligent Routing and Process Activation: After detection, the skill presents the result, requests confirmation, and then activates corresponding internal resource files:

  • Backend project → Activates the backend-dev.md process, covering the full backend development cycle from requirements analysis to implementation and interface documentation synchronization.
  • Frontend project → Activates the frontend-dev.md process, emphasizing page implementation based on interface documentation, and automatically references code-style.md to enforce a unified Vue3 template and file splitting standard.
  • Full-stack project → The skill further asks for the development focus (backend, frontend, or full-stack). Selecting "full-stack development" triggers sequential execution: first the backend process (producing interface docs), then the frontend process (consuming those docs), forming a cohesive development loop.

Scope and Considerations

While the companion covers common mainstream tech stacks, its detection rules are deterministic. For non-standard structures, hybrid stacks, or highly customized projects, automatic detection may be inaccurate, and will then rely on the user's manual specification. The skill itself doesn't contain code generation logic; its value lies in providing a process framework and state management. The quality of actual code implementation depends on the guidance within the sub-processes (like backend-dev.md). It is best suited as an initiation guide for team collaboration or systematic personal development.