菜单
Turn a plain-English vision or task into a verified, build-ready spec before any code. Locks the finish line, researches across channels, enforces the Evidence Standard, stops at the human gate. Adopted from CleanExpo/Fabel-Prompt-Engineer for the Synthex build process.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
The engineering navigation layer for Synthex — holds the mission, the current course, the rules of the ship, and routes work to the right existing specialist. Load at the START of any planning, prioritisation, "what's next", roadmap, scope, or new-feature decision. NEVER let work drift off the critical path or add capabilities the ship already carries (see dependency-discipline). NEVER claim done without the verification gate. NEVER merge to production or change prod data without a human gate. ALWAYS trace a task to the NorthStar, the live Linear epic, and an existing system before writing code.
Authenticated browser automation for Synthex — drive real Chrome to log in, screenshot, and audit dashboard/integration surfaces. Use for live visual verification, "audit the dashboard", "check what's connected", or closing the verification gate on /dashboard/* routes. Two backends: the Playwright MCP server (interactive, in-session tools) and the committed CLI scripts (scripts/browser/*.mjs, reliable + headless). RUNS WHERE THE BROWSER + NETWORK + AUTH EXIST — i.e. a local machine, not a network-restricted sandbox.
Synthex API testing enforcer. NEVER mock the database in integration tests — use real Supabase. NEVER skip the 401 (unauthenticated) or 403 (wrong org) test cases. NEVER use pnpm. ALWAYS structure tests as: 401 → 403 → 400 → 200/201 happy path. Activate on ANY request to write API tests, validate endpoints, add test coverage, or check test quality.
Synthex database operations enforcer. NEVER use prisma db push for schema changes — use migrate diff + db execute. NEVER add non-nullable columns without defaults. NEVER write Prisma queries without organizationId scope. ALWAYS use backward-compatible migrations and validate with prisma validate first. Activate on ANY request to change schema, write a query, create a migration, add a model, or modify database operations.
Synthex design system enforcer. NEVER use Inter as a heading font, purple (#8B5CF6) gradients on white, or generic glassmorphism without Synthex tokens. ALWAYS use Space Grotesk headings, #f97316 brand orange, #0f172a slate background, and the Synthex glass token set. Activate on ANY request involving UI, components, styling, layout, visual design, colour, typography, spacing, shadows, animations, or anything a user will see on screen.
Synthex security posture enforcer. NEVER apply generic OWASP checklists without grounding in Synthex's specific threat model. NEVER suggest any auth system other than Supabase. ALWAYS audit: SSRF via validateExternalUrl, JWT tier elevation via resolveVerifiedTier, CORS via CORS_ORIGIN exact-match, org-scope bypass in Prisma. Activate on ANY request to harden security, audit vulnerabilities, review auth patterns, check for injection risks, or assess an attack surface.
| name | fable-engine |
| description | Turn a plain-English vision or task into a verified, build-ready spec before any code. Locks the finish line, researches across channels, enforces the Evidence Standard, stops at the human gate. Adopted from CleanExpo/Fabel-Prompt-Engineer for the Synthex build process. |
Input: a vague idea or a non-trivial change in plain English. Output: a precise,
sourced, build-ready spec. You propose; the human decides. Pairs with
.claude/rules/fabel-evidence-standard.md and .claude/FABEL_PLAYBOOK.md.
Use it for: a new feature, a workstream/elevation wave, a risky refactor, or any multi-agent fan-out. Skip it for: a one-line fix or a conversational answer (Fabel directive 1 — act when you have enough info).
Restate the task as one testable sentence: "Done when ___." If several finish
lines are plausible, pick the most likely, state it, list the rejected ones.
Emit: [STATUS] finish-line: locked — <one sentence>
.claude/ rules that
constrain or accelerate the change. Docs are stale; the source is truth..claude/scratchpad, memories,
and open PRs for decisions and existing patterns (e.g. defineRoute,
getEffectiveOrganizationId, the deploy-pipeline gotchas).[UNCONFIRMED].Every finding and spec claim is tagged [VERIFIED] / [INFERENCE] /
[UNCONFIRMED] per fabel-evidence-standard.md. An untagged claim is a defect.
Draft the spec. Infer-and-tag rather than ask. Where info is genuinely missing, list ≤5 concrete, answerable questions.
Run boardroom / ask-the-board on the draft; append the combined critique as
a lens. Label it [INFERENCE] — persona synthesis, not fact. It feeds the gate,
never bypasses it.
Present the spec and stop. Nothing builds until the human approves. For the
agent fleet: the spec is the contract each subagent is dispatched against, and
the prod-deploy gate remains the founder's call.
Emit: [STATUS] gate: awaiting approval
apply_migration only, never prisma db push).[UNCONFIRMED] lands here.build:vercel, npm test -- --coverage, the integration gauntlet). Per
Fabel directive 5, a claim isn't done until its tool result says so.[STATUS] <subject>: <state>[ — detail] — subjects: finish-line,
channel:source, channel:prior-work, channel:web, synthesis, board,
gate.