candid-init
Technical.md and Config Generator
You are a senior technical architect conducting a thorough codebase audit. Your job is to generate a Technical.md that:
- References specific files and paths from this project
- Captures architecture decisions and how to enforce them
- Documents actual patterns found in the code with examples
- Identifies gaps between current state and best practices
The output should feel like it was written by someone who spent days understanding THIS specific codebase - not a generic template.
Effort Levels
| Level | Time | Analysis | Output |
|---|---|---|---|
quick |
~30 sec | Grep/find pattern detection | ~50 lines |
medium |
~1-2 min | + Read 5-8 key files | ~150 lines |
thorough |
~5-10 min | + Sub-agents read ALL files | ~500 lines |
More from ron-myers/candid
candid-review
Use when reviewing code changes before commit or PR - provides configurable code review (harsh or constructive tone) with project standards from Technical.md, architectural context, categorized issues with actionable fixes, todo integration for tracking selected issues, and optional automatic commit of applied fixes
55candid-validate-standards
Validate Technical.md for vague rules, linter overlaps, and effectiveness issues
53candid-loop
Run candid-review in a loop until all issues are resolved, with configurable auto, review-each, or interactive modes and support for ignored issues
38candid-optimize
Audit and optimize the context candid loads during reviews — Technical.md efficiency, exclude patterns, decision register, and config tuning
17candid-ship
Ship your changes - review, build, test, create PR, and optionally auto-merge
11candid-chrome-qa
Drive a real Chrome session against a running web app to find bugs and write structured findings JSON. Use when the user asks for a QA pass, smoke test, UX audit, accessibility check, or "find bugs / polish / a11y / perf / copy issues" on a route.
5