fullstack-development
暂无简介
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-12
- Stars
- ★ 1
- Forks
- 0
03 SKILL.md 正文
Fullstack Development
Use the existing repository, dependency environment and task contract. This procedure supplies execution order; it does not change acceptance requirements, file ownership or the selected technology stack.
Establish a runnable vertical slice
- Read the entry point, dependency manifest, API/data contract and existing tests. Record the exact working directory, executable and startup/test argv. Do not repeatedly enumerate the whole project once these are known.
- Implement one user flow through database, API and UI. Reuse the agreed API names and response shapes. Give producers explicit files and consumers explicit dependencies. Parallelize independent features after this contract.
- Name the owner of the service process and test database. Start the service, wait for its actual readiness response and record its address. A dead service is an environment prerequisite to repair, not evidence that all business assertions failed. Keep it available until dependent consumers finish.
Execute checks against the current implementation
Run existing unit/integration tests first. Exercise real HTTP and browser behavior required by the task, including persistence after reload and relevant permission/business boundaries. Record commands, exit codes, test case outcomes and tool receipts. A custom test adapter must summarize actual assertions in a format specified by the runtime test execution contract. Never add a constant success line or rewrite old failed receipts to satisfy the parser.
Repair one recorded gap
Use recovery_handoff.repair_procedures when present. Carry the original
criterion and command forward. Inspect only the named failure and necessary
implementation paths first:
- Missing summary: fix the test adapter/collector, then rerun its assertions.
- Missing execution: execute the required check after verifying prerequisites.
- Failed assertion: repair the responsible implementation, then rerun.
- Stale evidence: rerun on the current versions; do not refresh report dates.
- Zero tests: repair test discovery/selection before reporting success.
If a prerequisite diagnosis is now false, provide the concrete contradictory evidence. If the fix belongs to another owner, return the file, required change and recheck command to the Governor. A report-only successor does not discharge the test obligation. An implementation repair can be followed by a dependent tester carrying that same criterion.
Deliver after re-verification
Bind the final report to current test receipts and artifact versions. Preserve failed history separately. Assemble and publish only after the required checks pass. Report assembly, a completed node and a limited publication are not full acceptance. Do not start a new investigation or rewrite unaffected features merely because a recovery node has a new identifier.
04 同仓库更多 Skills
travel-device-coordination
Prepare multi-device business travel by organizing schedules, documents, sensitive data placement, connectivity, power, offline materials, and risks.
supply-chain-planning
Build constrained supply, production, inventory, and logistics plans with scenarios, sensitivity analysis, and exception replanning.
software-backend
Build and review production backend systems with explicit API, data, authorization, observability, testing, and deployment contracts.
scientific-research
Conduct evidence-backed literature analysis, hypothesis generation, baseline reproduction, minimal experiments, and falsifiable evaluation.
rag-retrieval
Design and evaluate production RAG pipelines with parsing, chunking, hybrid retrieval, reranking, citations, and multimodal context.
patent-analysis
Analyze prior art and draft patent materials with feature mapping, claim support, terminology consistency, and enablement checks.