一键导入
templates
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
Linting and validation principles for code quality enforcement.
Auto-evolved skill containing project-specific architectural idioms extracted from the developer's own code decisions. Generated by skill_evolution.js. Commit this file to share your Engineering Culture across the team. Every agent MUST respect these idioms above generic defaults.
Ingests test logs and identifies root causes across multiple failing test files. Provides actionable fix recommendations.
Distilled Fabel-5 cognitive intelligence protocol. Injects epistemic reasoning, coding discipline, design evaluation cascades, and orchestration patterns into any AI model. Load this skill to make any model think, reason, code, and design like Fabel-5. Activates for complex builds, code generation, design tasks, and multi-agent orchestration.
Tribunal Agent Kit thinking and cognitive reasoning rules. Helps agents structure their thoughts and follow protocols.
| name | templates |
| description | Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks. |
| allowed-tools | Read, Glob, Grep |
Read ONLY the template matching user's project type!
| Template | Tech Stack | When to Use |
|---|---|---|
| nextjs-fullstack | Next.js + Prisma | Full-stack web app |
| nextjs-saas | Next.js + Stripe | SaaS product |
| nextjs-static | Next.js + Framer | Landing page |
| express-api | Express + JWT | REST API |
| python-fastapi | FastAPI | Python API |
| react-native-app | Expo + Zustand | Mobile app |
| flutter-app | Flutter + Riverpod | Cross-platform |
| electron-desktop | Electron + React | Desktop app |
| chrome-extension | Chrome MV3 | Browser extension |
| cli-tool | Node.js + Commander | CLI app |
| monorepo-turborepo | Turborepo + pnpm | Monorepo |
| astro-static | Astro + MDX | Blog / Docs |
| Pattern | What AI Does Wrong | What Is Actually Correct |
|---|---|---|
| [domain-specific trap 1] | [hallucination] | [correct behavior] |
| [domain-specific trap 2] | [hallucination] | [correct behavior] |
| [domain-specific trap 3] | [hallucination] | [correct behavior] |
Before producing any output, verify:
✅ Did I read the actual files before making claims about them? ✅ Did I verify all method names against official documentation? ✅ Did I add // VERIFY: on any uncertain API calls? ✅ Are all imports from packages that actually exist in package.json? ✅ Did I test my logic with edge cases (null, empty, 0, max)? ✅ Did I avoid generating code for more than one module at a time? ✅ Am I working from evidence, not assumption?
VERIFY: Read the actual codebase before writing anything BUILD: Generate the smallest meaningful unit of code CONFIRM: Verify the output is correct before presenting
| Pattern | What AI Does Wrong | What Is Actually Correct |
|---|---|---|
| [domain-specific trap 1] | [hallucination] | [correct behavior] |
| [domain-specific trap 2] | [hallucination] | [correct behavior] |
| [domain-specific trap 3] | [hallucination] | [correct behavior] |
Before producing any output, verify:
✅ Did I read the actual files before making claims about them? ✅ Did I verify all method names against official documentation? ✅ Did I add // VERIFY: on any uncertain API calls? ✅ Are all imports from packages that actually exist in package.json? ✅ Did I test my logic with edge cases (null, empty, 0, max)? ✅ Did I avoid generating code for more than one module at a time? ✅ Am I working from evidence, not assumption?
VERIFY: Read the actual codebase before writing anything BUILD: Generate the smallest meaningful unit of code CONFIRM: Verify the output is correct before presenting
You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.