dinhanhthi
- 120 skills
- 0 followers
- 4 repo stars
- 3 days ago last updated
- ▌ Cf Commit · dinhanhthi bundleSmart conventional commit with diff analysis. Triggers: "commit this", "commit my changes", "save my work", "create a commit", "git commit", "stage and commit".
- ▌ Cf Design · dinhanhthi bundleUI 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".
- ▌ Cf Review · dinhanhthi bundleDispatch 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.
- ▌ Cf Session · dinhanhthi bundleSave 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".
- ▌ Cf Later Do · dinhanhthiWork 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).
- ▌ Cf Optimize · dinhanhthiStructured 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).
- ▌ Cf Remember · dinhanhthiSave 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).
- ▌ Cf Research · dinhanhthi bundleIn-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".
- ▌ Cf Review In · dinhanhthiCollect 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".
- ▌ Cf Sys Debug · dinhanhthiSystematic 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).
- ▌ Cf Checkpoint · dinhanhthiSave 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.
- ▌ Cf Review Out · dinhanhthi bundleGenerate 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".
- ▌ Cf Plan Resume · dinhanhthiResume 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).
- ▌ Cf Plan Review · dinhanhthi bundleReview 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).
- ▌ Cf Verification · dinhanhthiCompletion 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.
- ▌ Cf Checkpoint From · dinhanhthiLoad 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).
- ▌
- ▌
- ▌
- ▌