cf-help
SolidAnswer questions about Coding Friend — skills, agents, workflows, setup. Auto-invoke when the user asks about Coding Friend capabilities, available skills, how to use a skill, what skills/agents/commands exist, how it works, or how to configure it — e.g. "what skills are available?", "how does coding friend work?", "what can you do?", "list all skills", "what agents exist?", "how do I use cf-plan?", "what is cf-tdd?", "what does cf-fix do?", "which skill should I use?", "how do I get started?", "coding friend features/setup", "does X require the CLI?", "what works without coding-friend-cli?", "is the CLI required?". Do NOT auto-invoke for general coding questions unrelated to Coding Friend itself.
Install
Quality Score: 79/100
Skill Content
Details
- Author
- dinhanhthi
- Repository
- dinhanhthi/coding-friend
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
cf-teach
Personal teacher skill — after any task, explains what happened in a conversational, storytelling way (like a sharp friend over coffee). Covers: approach taken, alternatives rejected, how parts connect, tools used, tradeoffs, mistakes made, pitfalls to watch, expert observations, and transferable lessons. Unlike $cf-learn (concise structured reference notes), this creates a narrative deep-dive for the human to truly understand what happened and why.
cf-tdd
Use when writing new production code, adding features, implementing changes, or refactoring existing code — e.g. "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this", "clean up this code", "extract into a module", "simplify this function", "scaffold", "write a test", "add tests", "create a component", "implement the API", "add a route", "write a service", "create the handler". Also auto-invoke when the conversation transitions from planning/discussion to actual code writing — any time production code is about to be written, this skill MUST be loaded first. By default uses direct implementation (no new tests written). TDD is enabled when `--add-tests` is present or config `tdd: true`. This is the gate for all code writing in the project. Do NOT auto-invoke for documentation-only changes, config edits, non-code file updates, or when the user is only asking questions about code without requesting changes.
cf-ask
Quick Q&A about codebase — explores code to answer, saves to docs/memory. Use when the user asks a focused question about the project — e.g. "how does X work?", "where is Y defined?", "what's the flow for Z?", "explain this module", "how are these connected?", "what pattern does this use?", "why is this done this way?". Unlike $cf-research (deep multi-doc output), this gives a single focused answer.