Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

dinhanhthi

@dinhanhthi source repo

85 published skills

  1. ▌
    Cf Ask 2 · dinhanhthi bundle
    Quick Q&A about the codebase → docs/memory. Use for focused project questions — e.g. "how does X work?", "where is Y defined?", "what's the flow for Z?", "explain this module", "why is this done this way?". Unlike $cf-research, one answer.
    0
    installs
  2. ▌
    Cf Fix 2 · dinhanhthi
    Quick bug-fix workflow — reproduce, find the root cause, fix via cf-implementer, verify, auto-review. TRIGGER — the user reports a bug or broken behavior: "fix this", "it's broken", "not working", "there's a bug", "this crashes", "debug this", "it throws", "failing test", "regression", "unexpected behavior"; a pasted stack trace or error message. SKIP — new features (use cf-plan or cf-tdd), performance complaints (use cf-optimize), and recurring or hard-to-reproduce bugs after a failed fix (use cf-sys-debug).
    0
    installs
  3. ▌
    Cf Tdd 2 · dinhanhthi bundle
    Gate before writing production code — direct implementation by default, TDD (RED→GREEN→REFACTOR) with `--add-tests` or config `tdd: true`. TRIGGER — any new feature, implementation, or refactor: "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this", "write a test", "add tests", "create a component", "implement the API", "add a route"; also when planning shifts into writing code — load this first. SKIP — docs-only changes, config edits, non-code files, or questions with no requested change.
    0
    installs
  4. ▌
    Cf Help 2 · dinhanhthi bundle
    Answer questions about Coding Friend itself — skills, agents, hooks, CLI, config, memory, hosts, parameters. TRIGGER — "what skills are available?", "how does coding friend work?", "list all skills", "how do I use cf-plan?", "what is cf-tdd?", "is the CLI required?", or any question about a cf-* name, flag, hook, or config key. SKIP — general coding questions unrelated to Coding Friend, and requests to run a skill (invoke that skill instead).
    0
    installs
  5. ▌
    Cf Plan 2 · dinhanhthi bundle
    Brainstorm and write an implementation plan before coding. TRIGGER — the user wants to plan, build, create, or implement something: "let's build", "let's create", "add feature", "implement", "set up", "design a solution", "architect", "scaffold", "plan out", "what's the best way to build"; any multi-step or multi-file work that needs sequencing. SKIP — a single obvious edit, a reported bug (use cf-fix), deciding whether to build at all (use $cf-advise), or resuming an existing plan (use $cf-plan-resume).
    0
    installs
  6. ▌
    Cf Scan 2 · dinhanhthi bundle
    Scan the project and populate memory (architecture, conventions, stack, features). Triggers: "scan the project", "scan the codebase", "bootstrap memory", "populate memory", "analyze the project". Token-heavy — always warn before proceeding.
    0
    installs
  7. ▌
    Cf Ship 2 · dinhanhthi
    Verify, commit, push, and create a PR. Triggers: "ship it", "push and create PR", "let's ship", "create a PR", "open a pull request", "ready to merge". Supports --dry-run.
    0
    installs
  8. ▌
    Cf Warm 2 · dinhanhthi
    Catch up after absence — summarize git history for a user. Triggers: "warm up", "catch me up", "what happened while I was away", "summarize recent changes", "what changed since I left".
    0
    installs
  9. ▌
    Cf Learn 2 · dinhanhthi bundle
    Extract educational notes for the human from the conversation (unlike $cf-remember, which stores project memory for AI recall). TRIGGER — substantial new technical knowledge, a debugging breakthrough, an architecture decision explained, or a complex explanation worth keeping; the user says "explain what we learned", "make notes on this", "cf-learn". SKIP — trivial edits, typo fixes, routine operations, or knowledge that belongs in project memory rather than learning notes (use $cf-remember).
    0
    installs
  10. ▌
    Cf Teach 2 · dinhanhthi
    Personal teacher — after a task, explains what happened as a conversational narrative (approach, alternatives, tradeoffs, pitfalls, lessons). Unlike $cf-learn (structured notes), this is a deep-dive so the human understands what happened and why.
    0
    installs
  11. ▌
    Cf Advise 2 · dinhanhthi
    Decision advisory via structured interview — never writes code or plans. Use when the user wants help DECIDING — e.g. "should I", "is X worth it", "which approach", "help me decide between A and B", "am I overthinking this", "what would you recommend", "pros and cons of". Unlike $cf-plan (builds) or $cf-ask (looks up code), this only advises.
    0
    installs
  12. ▌
    Cf Commit 2 · dinhanhthi bundle
    Smart conventional commit with diff analysis. Triggers: "commit this", "commit my changes", "save my work", "create a commit", "git commit", "stage and commit".
    0
    installs
  13. ▌
    Cf Design 2 · dinhanhthi bundle
    UI design workflow — scan patterns, design new UI, or modify UI consistently. Use to redesign a component/page, change colors/typography/style, or extract the design system. Triggers: "make it look like", "update the styling", "redesign this", "match the existing style", "add a dark mode", "make it more minimal".
    0
    installs
  14. ▌
    Cf Review 2 · dinhanhthi bundle
    Dispatch a multi-agent code review of the current changes and report Critical / Important / Suggestions / Summary. TRIGGER — "review this", "review my changes", "check the code", "code review", "any issues with this?", "review before merge", "review the diff"; reviewing specific files, commits, or branches; automatically after cf-plan, cf-fix, and cf-optimize complete. SKIP — reviewing a plan document (use $cf-plan-review), quick questions about how code works (use $cf-ask), and formatting-only changes.
    0
    installs
  15. ▌
    Cf Session 2 · dinhanhthi
    Continue or branch Codex conversations with the native session controls. Use when the user asks to resume, continue, fork, or restore a Codex session. Codex owns its transcript format, so Coding Friend does not copy or rewrite session JSONL files.
    0
    installs
  16. ▌
    Cf Later Do 2 · dinhanhthi
    Work through deferred side-tasks in docs/later/. Triggers: "do the later tasks", "process docs/later", "work through the backlog", "what did we defer", "resolve deferred items", "cf-later-do". Routes to $cf-fix or $cf-plan; removes the file only after verified-done. Slash-only — NOT auto-invoked. Does NOT capture new items (that is capture-later.sh).
    0
    installs
  17. ▌
    Cf Optimize 2 · dinhanhthi
    Structured performance work — baseline, analyze, optimize, measure, compare. TRIGGER — "this is slow", "make it faster", "optimize", "performance", "bottleneck", "too many queries", "high latency", "memory leak", "speed up", "timeout", "N+1", or any request to reduce time, memory, or query count with numbers to prove it. SKIP — minor refactors, readability or style changes, and correctness bugs that are not performance-related (use cf-fix).
    0
    installs
  18. ▌
    Cf Remember 2 · dinhanhthi
    Save project knowledge to docs/memory for AI recall (unlike $cf-learn, which writes educational notes for the human). TRIGGER — "remember this", "save this to memory", "document what we did", "capture this decision", "write this down", "note this", "record this convention"; after a non-obvious bug fix → bugs/, an architecture decision → decisions/, a new convention → conventions/, a feature flow or gotcha → features/. SKIP — trivial fixes, simple config changes, or educational exchanges (use $cf-learn).
    0
    installs
  19. ▌
    Cf Research 2 · dinhanhthi bundle
    In-depth research with web search and structured output. Triggers: "research this", "look into this library", "investigate how X works", "compare these options", "best practices for", "deep dive into", "study this technology".
    0
    installs
  20. ▌
    Cf Ask 3 · dinhanhthi bundle
    Quick Q&A about the codebase → docs/memory. Use for focused project questions — e.g. "how does X work?", "where is Y defined?", "what's the flow for Z?", "explain this module", "why is this done this way?". Unlike /cf-research, one answer.
    0
    installs
  21. ▌
    Cf Fix 3 · dinhanhthi
    Quick bug-fix workflow — reproduce, find the root cause, fix via cf-implementer, verify, auto-review. TRIGGER — the user reports a bug or broken behavior: "fix this", "it's broken", "not working", "there's a bug", "this crashes", "debug this", "it throws", "failing test", "regression", "unexpected behavior"; a pasted stack trace or error message. SKIP — new features (use cf-plan or cf-tdd), performance complaints (use cf-optimize), and recurring or hard-to-reproduce bugs after a failed fix (use cf-sys-debug).
    0
    installs
  22. ▌
    Cf Tdd 3 · dinhanhthi bundle
    Gate before writing production code — direct implementation by default, TDD (RED→GREEN→REFACTOR) with `--add-tests` or config `tdd: true`. TRIGGER — any new feature, implementation, or refactor: "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this", "write a test", "add tests", "create a component", "implement the API", "add a route"; also when planning shifts into writing code — load this first. SKIP — docs-only changes, config edits, non-code files, or questions with no requested change.
    0
    installs
  23. ▌
    Cf Review In 2 · dinhanhthi
    Collect and act on an external AI review. Reads the result file, presents findings, offers to fix. Triggers: "review in", "collect review", "check review results", "cf-review-in", "import review".
    0
    installs
  24. ▌
    Cf Sys Debug 2 · dinhanhthi
    Systematic 4-phase debugging — root cause, hypothesis testing, regression-guarded fix, mandatory bug doc. TRIGGER — non-trivial or recurring bugs: "still broken", "same error again", "came back", flaky/intermittent/race, "used to work, now broken", hard-to-reproduce, works locally but fails in CI, "find the root cause", "investigate", "diagnose", "why is this happening"; prefer over cf-fix once a fix has already failed. SKIP — trivial typos, one-line fixes, obvious config errors, or first-time simple bugs (use cf-fix).
    0
    installs
  25. ▌
    Cf Help 3 · dinhanhthi bundle
    Answer questions about Coding Friend itself — skills, agents, hooks, CLI, config, memory, hosts, parameters. TRIGGER — "what skills are available?", "how does coding friend work?", "list all skills", "how do I use cf-plan?", "what is cf-tdd?", "is the CLI required?", or any question about a cf-* name, flag, hook, or config key. SKIP — general coding questions unrelated to Coding Friend, and requests to run a skill (invoke that skill instead).
    0
    installs
  26. ▌
    Cf Plan 3 · dinhanhthi bundle
    Brainstorm and write an implementation plan before coding. TRIGGER — the user wants to plan, build, create, or implement something: "let's build", "let's create", "add feature", "implement", "set up", "design a solution", "architect", "scaffold", "plan out", "what's the best way to build"; any multi-step or multi-file work that needs sequencing. SKIP — a single obvious edit, a reported bug (use cf-fix), deciding whether to build at all (use /cf-advise), or resuming an existing plan (use /cf-plan-resume).
    0
    installs
  27. ▌
    Cf Scan 3 · dinhanhthi bundle
    Scan the project and populate memory (architecture, conventions, stack, features). Triggers: "scan the project", "scan the codebase", "bootstrap memory", "populate memory", "analyze the project". Token-heavy — always warn before proceeding.
    0
    installs
  28. ▌
    Cf Ship 3 · dinhanhthi
    Verify, commit, push, and create a PR. Triggers: "ship it", "push and create PR", "let's ship", "create a PR", "open a pull request", "ready to merge". Supports --dry-run.
    0
    installs
  29. ▌
    Cf Warm 3 · dinhanhthi
    Catch up after absence — summarize git history for a user. Triggers: "warm up", "catch me up", "what happened while I was away", "summarize recent changes", "what changed since I left".
    0
    installs
  30. ▌
    Cf Checkpoint 2 · dinhanhthi
    Save a conversation checkpoint (goal, decisions, breaking changes, next steps) for a DIFFERENT conversation. Triggers: "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (same chat) or $cf-remember (project facts). Slash-only — does NOT auto-invoke.
    0
    installs
  31. ▌
    Cf Review Out 2 · dinhanhthi bundle
    Generate a review prompt for an external AI (Gemini, Codex, ChatGPT, or a human). Triggers: "get a second opinion", "external review", "review out", "send for review", "cf-review-out", "prepare review for gemini".
    0
    installs
  32. ▌
    Cf Learn 3 · dinhanhthi bundle
    Extract educational notes for the human from the conversation (unlike /cf-remember, which stores project memory for AI recall). TRIGGER — substantial new technical knowledge, a debugging breakthrough, an architecture decision explained, or a complex explanation worth keeping; the user says "explain what we learned", "make notes on this", "cf-learn". SKIP — trivial edits, typo fixes, routine operations, or knowledge that belongs in project memory rather than learning notes (use /cf-remember).
    0
    installs
  33. ▌
    Cf Teach 3 · dinhanhthi
    Personal teacher — after a task, explains what happened as a conversational narrative (approach, alternatives, tradeoffs, pitfalls, lessons). Unlike /cf-learn (structured notes), this is a deep-dive so the human understands what happened and why.
    0
    installs
  34. ▌
    Cf Plan Resume 2 · dinhanhthi
    Resume an existing $cf-plan from where execution last stopped. Triggers: "resume the plan", "continue the plan", "pick up where we left off", "finish the plan", "resume <slug>". Requires a plan under docs/plans/. Does NOT create new plans (use $cf-plan).
    0
    installs
  35. ▌
    Cf Plan Review 2 · dinhanhthi bundle
    Review a saved $cf-plan folder with a fresh reviewer before implementing; triggers "review the plan", "plan review", "second opinion on the plan", "check the plan before implementing", "cf-plan-review"; does NOT review code (use $cf-review).
    0
    installs
  36. ▌
    Cf Advise 3 · dinhanhthi
    Decision advisory via structured interview — never writes code or plans. Use when the user wants help DECIDING — e.g. "should I", "is X worth it", "which approach", "help me decide between A and B", "am I overthinking this", "what would you recommend", "pros and cons of". Unlike /cf-plan (builds) or /cf-ask (looks up code), this only advises.
    0
    installs
  37. ▌
    Cf Commit 3 · dinhanhthi bundle
    Smart conventional commit with diff analysis. Triggers: "commit this", "commit my changes", "save my work", "create a commit", "git commit", "stage and commit".
    0
    installs
  38. ▌
    Cf Design 3 · dinhanhthi bundle
    UI design workflow — scan patterns, design new UI, or modify UI consistently. Use to redesign a component/page, change colors/typography/style, or extract the design system. Triggers: "make it look like", "update the styling", "redesign this", "match the existing style", "add a dark mode", "make it more minimal".
    0
    installs
  39. ▌
    Cf Review 3 · dinhanhthi bundle
    Dispatch a multi-agent code review of the current changes and report Critical / Important / Suggestions / Summary. TRIGGER — "review this", "review my changes", "check the code", "code review", "any issues with this?", "review before merge", "review the diff"; reviewing specific files, commits, or branches; automatically after cf-plan, cf-fix, and cf-optimize complete. SKIP — reviewing a plan document (use /cf-plan-review), quick questions about how code works (use /cf-ask), and formatting-only changes.
    0
    installs
  40. ▌
    Cf Verification 2 · dinhanhthi
    Completion gate — demands fresh verification evidence (test run, command output, manual check) before any claim that work is done. TRIGGER — about to say "done", "complete", "fixed", "passing", "ready to commit" or "ready to ship", or to summarize finished work; the end of any cf-tdd, cf-fix, cf-plan, or cf-optimize run; the user asks "is it done?" or "does it work?". SKIP — mid-task progress notes, exploratory or read-only answers, and plans that have not been implemented yet.
    0
    installs
  41. ▌
    Cf Session 3 · dinhanhthi
    Continue or resume Google Antigravity conversations with the native session controls. Use when the user asks to resume, continue, or restore an Antigravity session. Antigravity owns its transcript format, so Coding Friend does not copy or rewrite session files.
    0
    installs
  42. ▌
    Cf Later Do 3 · dinhanhthi
    Work through deferred side-tasks in docs/later/. Triggers: "do the later tasks", "process docs/later", "work through the backlog", "what did we defer", "resolve deferred items", "cf-later-do". Routes to /cf-fix or /cf-plan; removes the file only after verified-done. Slash-only — NOT auto-invoked. Does NOT capture new items (that is capture-later.sh).
    0
    installs
  43. ▌
    Cf Optimize 3 · dinhanhthi
    Structured performance work — baseline, analyze, optimize, measure, compare. TRIGGER — "this is slow", "make it faster", "optimize", "performance", "bottleneck", "too many queries", "high latency", "memory leak", "speed up", "timeout", "N+1", or any request to reduce time, memory, or query count with numbers to prove it. SKIP — minor refactors, readability or style changes, and correctness bugs that are not performance-related (use cf-fix).
    0
    installs
  44. ▌
    Cf Remember 3 · dinhanhthi
    Save project knowledge to docs/memory for AI recall (unlike /cf-learn, which writes educational notes for the human). TRIGGER — "remember this", "save this to memory", "document what we did", "capture this decision", "write this down", "note this", "record this convention"; after a non-obvious bug fix → bugs/, an architecture decision → decisions/, a new convention → conventions/, a feature flow or gotcha → features/. SKIP — trivial fixes, simple config changes, or educational exchanges (use /cf-learn).
    0
    installs
  45. ▌
    Cf Research 3 · dinhanhthi bundle
    In-depth research with web search and structured output. Triggers: "research this", "look into this library", "investigate how X works", "compare these options", "best practices for", "deep dive into", "study this technology".
    0
    installs
  46. ▌
    Cf Review In 3 · dinhanhthi
    Collect and act on an external AI review. Reads the result file, presents findings, offers to fix. Triggers: "review in", "collect review", "check review results", "cf-review-in", "import review".
    0
    installs
  47. ▌
    Cf Sys Debug 3 · dinhanhthi
    Systematic 4-phase debugging — root cause, hypothesis testing, regression-guarded fix, mandatory bug doc. TRIGGER — non-trivial or recurring bugs: "still broken", "same error again", "came back", flaky/intermittent/race, "used to work, now broken", hard-to-reproduce, works locally but fails in CI, "find the root cause", "investigate", "diagnose", "why is this happening"; prefer over cf-fix once a fix has already failed. SKIP — trivial typos, one-line fixes, obvious config errors, or first-time simple bugs (use cf-fix).
    0
    installs
  48. ▌
    Cf Checkpoint From 2 · dinhanhthi
    Load a saved checkpoint as working context, then do the next ask. Triggers: "resume from checkpoint", "load checkpoint", "continue from checkpoint", "cf-checkpoint-from", "restore conversation context". First word is the slug; `--recap` prints a summary. Does NOT create checkpoints (use $cf-checkpoint).
    0
    installs
  49. ▌
    Cf Checkpoint 3 · dinhanhthi
    Save a conversation checkpoint (goal, decisions, breaking changes, next steps) for a DIFFERENT conversation. Triggers: "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (same chat) or /cf-remember (project facts). Slash-only — does NOT auto-invoke.
    0
    installs
  50. ▌
    Cf Review Out 3 · dinhanhthi bundle
    Generate a review prompt for an external AI (Gemini, Codex, ChatGPT, or a human). Triggers: "get a second opinion", "external review", "review out", "send for review", "cf-review-out", "prepare review for gemini".
    0
    installs
  51. ▌
    Cf Plan Resume 3 · dinhanhthi
    Resume an existing /cf-plan from where execution last stopped. Triggers: "resume the plan", "continue the plan", "pick up where we left off", "finish the plan", "resume <slug>". Requires a plan under docs/plans/. Does NOT create new plans (use /cf-plan).
    0
    installs
  52. ▌
    Cf Plan Review 3 · dinhanhthi bundle
    Review a saved /cf-plan folder with a fresh reviewer before implementing; triggers "review the plan", "plan review", "second opinion on the plan", "check the plan before implementing", "cf-plan-review"; does NOT review code (use /cf-review).
    0
    installs
  53. ▌
    Cf Verification 3 · dinhanhthi
    Completion gate — demands fresh verification evidence (test run, command output, manual check) before any claim that work is done. TRIGGER — about to say "done", "complete", "fixed", "passing", "ready to commit" or "ready to ship", or to summarize finished work; the end of any cf-tdd, cf-fix, cf-plan, or cf-optimize run; the user asks "is it done?" or "does it work?". SKIP — mid-task progress notes, exploratory or read-only answers, and plans that have not been implemented yet.
    0
    installs
  54. ▌
    Cf Checkpoint From 3 · dinhanhthi
    Load a saved checkpoint as working context, then do the next ask. Triggers: "resume from checkpoint", "load checkpoint", "continue from checkpoint", "cf-checkpoint-from", "restore conversation context". First word is the slug; `--recap` prints a summary. Does NOT create checkpoints (use /cf-checkpoint).
    0
    installs
  55. ▌
    Cf Ask · dinhanhthi bundle
    Quick Q&A about the codebase → docs/memory. Use for focused project questions — e.g. "how does X work?", "where is Y defined?", "what's the flow for Z?", "explain this module", "why is this done this way?". Unlike /cf-research, one answer.
    0
    installs
  56. ▌
    Cf Fix · dinhanhthi
    Quick bug-fix workflow — reproduce, find the root cause, fix via cf-implementer, verify, auto-review. TRIGGER — the user reports a bug or broken behavior: "fix this", "it's broken", "not working", "there's a bug", "this crashes", "debug this", "it throws", "failing test", "regression", "unexpected behavior"; a pasted stack trace or error message. SKIP — new features (use cf-plan or cf-tdd), performance complaints (use cf-optimize), and recurring or hard-to-reproduce bugs after a failed fix (use cf-sys-debug).
    0
    installs
  57. ▌
    Cf Tdd · dinhanhthi bundle
    Gate before writing production code — direct implementation by default, TDD (RED→GREEN→REFACTOR) with `--add-tests` or config `tdd: true`. TRIGGER — any new feature, implementation, or refactor: "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this", "write a test", "add tests", "create a component", "implement the API", "add a route"; also when planning shifts into writing code — load this first. SKIP — docs-only changes, config edits, non-code files, or questions with no requested change.
    0
    installs
  58. ▌
    Cf Help · dinhanhthi bundle
    Answer questions about Coding Friend itself — skills, agents, hooks, CLI, config, memory, hosts, parameters. TRIGGER — "what skills are available?", "how does coding friend work?", "list all skills", "how do I use cf-plan?", "what is cf-tdd?", "is the CLI required?", or any question about a cf-* name, flag, hook, or config key. SKIP — general coding questions unrelated to Coding Friend, and requests to run a skill (invoke that skill instead).
    0
    installs
  59. ▌
    Cf Plan · dinhanhthi bundle
    Brainstorm and write an implementation plan before coding. TRIGGER — the user wants to plan, build, create, or implement something: "let's build", "let's create", "add feature", "implement", "set up", "design a solution", "architect", "scaffold", "plan out", "what's the best way to build"; any multi-step or multi-file work that needs sequencing. SKIP — a single obvious edit, a reported bug (use cf-fix), deciding whether to build at all (use /cf-advise), or resuming an existing plan (use /cf-plan-resume).
    0
    installs
  60. ▌
    Cf Scan · dinhanhthi bundle
    Scan the project and populate memory (architecture, conventions, stack, features). Triggers: "scan the project", "scan the codebase", "bootstrap memory", "populate memory", "analyze the project". Token-heavy — always warn before proceeding.
    0
    installs
  61. ▌
    Cf Ship · dinhanhthi
    Verify, commit, push, and create a PR. Triggers: "ship it", "push and create PR", "let's ship", "create a PR", "open a pull request", "ready to merge". Supports --dry-run.
    0
    installs
  62. ▌
    Cf Warm · dinhanhthi
    Catch up after absence — summarize git history for a user. Triggers: "warm up", "catch me up", "what happened while I was away", "summarize recent changes", "what changed since I left".
    0
    installs
  63. ▌
    Cf Learn · dinhanhthi bundle
    Extract educational notes for the human from the conversation (unlike /cf-remember, which stores project memory for AI recall). TRIGGER — substantial new technical knowledge, a debugging breakthrough, an architecture decision explained, or a complex explanation worth keeping; the user says "explain what we learned", "make notes on this", "cf-learn". SKIP — trivial edits, typo fixes, routine operations, or knowledge that belongs in project memory rather than learning notes (use /cf-remember).
    0
    installs
  64. ▌
    Cf Teach · dinhanhthi
    Personal teacher — after a task, explains what happened as a conversational narrative (approach, alternatives, tradeoffs, pitfalls, lessons). Unlike /cf-learn (structured notes), this is a deep-dive so the human understands what happened and why.
    0
    installs
  65. ▌
    Cf Advise · dinhanhthi
    Decision advisory via structured interview — never writes code or plans. Use when the user wants help DECIDING — e.g. "should I", "is X worth it", "which approach", "help me decide between A and B", "am I overthinking this", "what would you recommend", "pros and cons of". Unlike /cf-plan (builds) or /cf-ask (looks up code), this only advises.
    0
    installs
  66. ▌
    Cf Commit · dinhanhthi bundle
    Smart conventional commit with diff analysis. Triggers: "commit this", "commit my changes", "save my work", "create a commit", "git commit", "stage and commit".
    0
    installs
  67. ▌
    Cf Design · dinhanhthi bundle
    UI design workflow — scan patterns, design new UI, or modify UI consistently. Use to redesign a component/page, change colors/typography/style, or extract the design system. Triggers: "make it look like", "update the styling", "redesign this", "match the existing style", "add a dark mode", "make it more minimal".
    0
    installs
  68. ▌
    Cf Review · dinhanhthi bundle
    Dispatch a multi-agent code review of the current changes and report Critical / Important / Suggestions / Summary. TRIGGER — "review this", "review my changes", "check the code", "code review", "any issues with this?", "review before merge", "review the diff"; reviewing specific files, commits, or branches; automatically after cf-plan, cf-fix, and cf-optimize complete. SKIP — reviewing a plan document (use /cf-plan-review), quick questions about how code works (use /cf-ask), and formatting-only changes.
    0
    installs
  69. ▌
    Cf Session · dinhanhthi bundle
    Save the current session to docs/sessions/ for cross-machine resume. Triggers: "save this session", "continue on another machine", "export this conversation", "sync this session", "bookmark this session".
    0
    installs
  70. ▌
    Cf Later Do · dinhanhthi
    Work through deferred side-tasks in docs/later/. Triggers: "do the later tasks", "process docs/later", "work through the backlog", "what did we defer", "resolve deferred items", "cf-later-do". Routes to /cf-fix or /cf-plan; removes the file only after verified-done. Slash-only — NOT auto-invoked. Does NOT capture new items (that is capture-later.sh).
    0
    installs
  71. ▌
    Cf Optimize · dinhanhthi
    Structured performance work — baseline, analyze, optimize, measure, compare. TRIGGER — "this is slow", "make it faster", "optimize", "performance", "bottleneck", "too many queries", "high latency", "memory leak", "speed up", "timeout", "N+1", or any request to reduce time, memory, or query count with numbers to prove it. SKIP — minor refactors, readability or style changes, and correctness bugs that are not performance-related (use cf-fix).
    0
    installs
  72. ▌
    Cf Remember · dinhanhthi
    Save project knowledge to docs/memory for AI recall (unlike /cf-learn, which writes educational notes for the human). TRIGGER — "remember this", "save this to memory", "document what we did", "capture this decision", "write this down", "note this", "record this convention"; after a non-obvious bug fix → bugs/, an architecture decision → decisions/, a new convention → conventions/, a feature flow or gotcha → features/. SKIP — trivial fixes, simple config changes, or educational exchanges (use /cf-learn).
    0
    installs
  73. ▌
    Cf Research · dinhanhthi bundle
    In-depth research with web search and structured output. Triggers: "research this", "look into this library", "investigate how X works", "compare these options", "best practices for", "deep dive into", "study this technology".
    0
    installs
  74. ▌
    Cf Review In · dinhanhthi
    Collect and act on an external AI review. Reads the result file, presents findings, offers to fix. Triggers: "review in", "collect review", "check review results", "cf-review-in", "import review".
    0
    installs
  75. ▌
    Cf Sys Debug · dinhanhthi
    Systematic 4-phase debugging — root cause, hypothesis testing, regression-guarded fix, mandatory bug doc. TRIGGER — non-trivial or recurring bugs: "still broken", "same error again", "came back", flaky/intermittent/race, "used to work, now broken", hard-to-reproduce, works locally but fails in CI, "find the root cause", "investigate", "diagnose", "why is this happening"; prefer over cf-fix once a fix has already failed. SKIP — trivial typos, one-line fixes, obvious config errors, or first-time simple bugs (use cf-fix).
    0
    installs
  76. ▌
    Cf Checkpoint · dinhanhthi
    Save a conversation checkpoint (goal, decisions, breaking changes, next steps) for a DIFFERENT conversation. Triggers: "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (same chat) or /cf-remember (project facts). Slash-only — does NOT auto-invoke.
    0
    installs
  77. ▌
    Cf Review Out · dinhanhthi bundle
    Generate a review prompt for an external AI (Gemini, Codex, ChatGPT, or a human). Triggers: "get a second opinion", "external review", "review out", "send for review", "cf-review-out", "prepare review for gemini".
    0
    installs
  78. ▌
    Cf Plan Resume · dinhanhthi
    Resume an existing /cf-plan from where execution last stopped. Triggers: "resume the plan", "continue the plan", "pick up where we left off", "finish the plan", "resume <slug>". Requires a plan under docs/plans/. Does NOT create new plans (use /cf-plan).
    0
    installs
  79. ▌
    Cf Plan Review · dinhanhthi bundle
    Review a saved /cf-plan folder with a fresh reviewer before implementing; triggers "review the plan", "plan review", "second opinion on the plan", "check the plan before implementing", "cf-plan-review"; does NOT review code (use /cf-review).
    0
    installs
  80. ▌
    Cf Verification · dinhanhthi
    Completion gate — demands fresh verification evidence (test run, command output, manual check) before any claim that work is done. TRIGGER — about to say "done", "complete", "fixed", "passing", "ready to commit" or "ready to ship", or to summarize finished work; the end of any cf-tdd, cf-fix, cf-plan, or cf-optimize run; the user asks "is it done?" or "does it work?". SKIP — mid-task progress notes, exploratory or read-only answers, and plans that have not been implemented yet.
    0
    installs
  81. ▌
    Cf Checkpoint From · dinhanhthi
    Load a saved checkpoint as working context, then do the next ask. Triggers: "resume from checkpoint", "load checkpoint", "continue from checkpoint", "cf-checkpoint-from", "restore conversation context". First word is the slug; `--recap` prints a summary. Does NOT create checkpoints (use /cf-checkpoint).
    0
    installs
  82. ▌
    Cf Plan Custom · dinhanhthi
    Before
    0
    installs
  83. ▌
    Cf Ship Custom · dinhanhthi bundle
    Before
    0
    installs
  84. ▌
    Cf Commit Custom · dinhanhthi
    Before
    0
    installs
  85. ▌
    Cf Review Custom · dinhanhthi
    After
    0
    installs