‹ 首页

fullstack-dev

@qianleigood · 收录于 昨天 · 上游提交 1 个月前

Use when work spans backend services and browser-facing behavior, including APIs, auth/session flows, uploads, CRUD/business workflows, realtime features, or production hardening.

场景全栈开发接口联调实时功能

适合你，如果你需要同时处理前端和后端逻辑，构建完整Web应用

/ 下载安装
https://github.com/qianleigood/crawclaw/tree/main/skills/fullstack-dev ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add qianleigood/crawclaw/fullstack-dev
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- qianleigood/crawclaw/fullstack-dev
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify qianleigood/crawclaw/fullstack-dev
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
30GitHub stars
~415最小装载
~16.6K含声明引用
~19.4K文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 f27e175 · 表述以原文为准
它做什么

装上后，Claude 会先询问或明确技术栈、服务类型、数据库等，说明架构决策，再按基线清单（如特性优先结构、验证配置、类型化错误处理、日志等）构建代码，最后验证构建和前后端集成。

什么时候触发

当任务涉及前后端边界，例如构建全栈应用、API、认证、上传、实时功能或生产加固时触发。

装好后可以这样说
Claude 会先问技术栈再开始编码。
会涵盖架构决策和集成验证。
技能原文 SKILL.md作者撰写 · MIT · f27e175

Full-Stack Development Practices

Use this skill when the task crosses the frontend/backend boundary.

Use this skill for
  • full-stack apps
  • backend + frontend integration
  • API or service scaffolding
  • auth, uploads, caching, background jobs
  • real-time features
  • production hardening
  • service boundary and module design

Do not use this skill for pure frontend styling/motion work or database-only schema work with no application-layer design.

Mandatory workflow
  1. Infer or clarify:
  2. stack
  3. service type
  4. database choice
  5. integration method
  6. real-time requirements
  7. auth strategy
  8. State architectural decisions before coding:
  9. project structure
  10. API client approach
  11. auth strategy
  12. real-time method
  13. error-handling strategy
  14. Build with the baseline checklist in mind:
  15. feature-first structure
  16. validated config
  17. typed error handling
  18. logging
  19. validation
  20. health endpoints
  21. graceful shutdown
  22. explicit CORS and security headers
  23. Verify before handoff:
  24. build
  25. smoke test
  26. frontend/backend integration
  27. real-time path when relevant
Working rules
  • Prefer the simplest architecture that still matches the stated requirements.
  • Do not hide business logic in controllers.
  • Keep frontend/backend contracts explicit.
  • Explain tradeoffs when multiple patterns are reasonable.
Read references as needed
  • references/core-architecture.md For feature structure, module boundaries, config, errors, and logging.
  • references/integration-patterns.md For API clients, uploads, auth flows, real-time choices, and boundary rules.
  • references/production-hardening.md For moving beyond prototype quality.
  • references/testing-strategy.md, references/release-checklist.md, references/technology-selection.md For verification and launch decisions.
  • references/api-design.md, references/auth-flow.md, references/db-schema.md, references/environment-management.md For subsystem-specific guidance.
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…