Use when users need to debug, modify, or extend the code-forge application's CLI commands, argument parsing, or CLI behavior. This includes adding new commands, fixing CLI bugs, updating command options, or troubleshooting CLI-related issues.
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling…
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it…
Reviews accessibility including WCAG, ARIA, keyboard navigation. Use when junior builds forms, buttons, modals, interactive elements, or asks "is this accessible", "a11y", "screen reader".
Reviews schema design, SQL queries, ORM patterns. Use when junior creates schema, writes queries, adds migrations, works with Prisma/MongoDB/PostgreSQL, or asks "is this SQL safe", "N+1", "index".
Guides systematic debugging through Protocol D (READ, ISOLATE, DOCS, HYPOTHESIZE, VERIFY). Use when junior says "stuck", "not working", "broken", "bug", "error", "crashed", "failing", "can't figure out", or expresses frustration. Do NOT use for general questions.
Triggers (all require explicit user request — do NOT activate just because a brain/ folder exists): (1) The user wants to set up project-level memory ("set up project brain", "scaffold project context", "init project brain", "建项目脑"). (2) The user is in a directory containing brain/ AND explicitly asks to resume /…
Learn by building — learning is the goal, building is the test. When the user wants to make something, first turn the product into scenario scripts, translate those into capability blocks, then cut a ladder of stages: stage 1 is a runnable MVP, every later stage adds one block and still runs. Each stage carries a…
Use right after writing or editing code or files for the user — before ending your turn — to quiz them on what was just built and confirm they actually understand it. Also triggers on "quiz me", "test my understanding", "check what I learned", "comprehension check", or recovering the understanding that vaporizes when…
Context window health check. Trigger with /ctx or phrases like "context check", "do I need a new conversation", "how much context left". Evaluates current context consumption and recommends whether to start a new conversation.
Cross-platform content distribution and growth strategy for DYA app across 10+ platforms (Xiaohongshu, Douyin, TikTok, Instagram Reels, X/Twitter, Reddit, Weibo, Bilibili, WeChat Video). Use when planning social media posts, distributing video content, optimizing for platform algorithms, writing platform-specific…
This file is the design source of truth for r3's route catalog and CLI usage — update it here when the surface changes. The wire shapes live in shared/types.ts (the contract itself); this is the map over them.
Cut an r3 release — draft the CHANGELOG entry, bump every version string in lockstep, commit, then cut the annotated vX.Y.Z tag on that commit (the release CI lifts the changelog section into the GitHub release notes). Use when the user wants to release a new version, bump the version, write or update the changelog…
This file is the design source of truth for r3's security posture — update it here when the posture changes. AGENTS.md carries only the one-line invariants; the reasoning lives here.
How Forge writes code, injected on every build step so the generated project stays coherent across phases. Use whenever writing or editing code in a Forge-governed project.
The gate at the end of a step — the user explains back what was built and why, before the step counts as finished. Use at the teach-back stage, after tests pass and the review is clean.
How Forge teaches and questions a decision — teach the concept, give options with a project-derived recommendation, then wait. Use at interrogation and planning stages, before any code is written.
Socratic debugging companion, at one of three intensities: lite, full (default), ultra. Instead of solving the problem, asks one question at a time until the user reaches the answer themselves. ACTIVATE ONLY ON EXPLICIT REQUEST — when the user invokes this skill, optionally naming one of those three levels, or…
Join and behave correctly in a Bothread room — a shared, human-governed space where you collaborate with other AI agents on one codebase. Use this when the user says they want you to join a Bothread session, gives you a Bothread session ID, or asks you to coordinate with other agents.
Join and behave correctly in a Bothread room — a shared, human-governed space where you collaborate with other AI agents on one codebase. Use this when the user says they want you to join a Bothread session, gives you a Bothread session ID, or asks you to coordinate with other agents.