clauDNA
Claudfather/clauDNA
Global Claude Code configuration — skills, agents, hooks, commands installed to ~/.claude/
Instalação
npx convez-ai Claudfather/clauDNA1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
README
A tradução para o português deste README ainda está na fila.
clauDNA
Claude Code plugin pack: curated skills, agents, and hooks distributed via the Claudfather marketplace.
Quick Start
Requires Claude Code (npm install -g @anthropic-ai/claude-code).
Inside Claude Code:
/plugin marketplace add Claudfather/clauDNA
/plugin install claudna@Claudfather
That's it. Skills become available as /claudna:<skill-name> (namespaced under the plugin). Tab completion works — type /claudna: and press Tab to browse, or /claudna:tech and Tab to narrow. Hooks (auto-format, pretooluse permission expansion, notifications) activate automatically when the plugin is enabled.
After install
Optional, in any order:
- Recommended
settings.jsontweaks — permissions, statusLine, sandbox config. See SETUP_GUIDE §3. - Snowflake setup — only if you use the Snowflake skills. See SETUP_GUIDE §5.
- Shell aliases — power-user worktree commands. See SETUP_GUIDE §6.
- Project setup — in any project, run
/claudna:init-projectto generateCLAUDE.md,CHANGELOG.md, and.claude/lessons.md.
Headless / CI / Docker
For bots, CI runners, and Docker images, drop a settings.json with enabledPlugins + extraKnownMarketplaces, then set CLAUDE_CODE_SYNC_PLUGIN_INSTALL=1 and run claude -p. Full recipe in SETUP_GUIDE §4.
What ships with the plugin
| Directory | Count | Contents |
|---|---|---|
skills/ | 52 | User-invocable slash commands |
agents/ | 8 | snowflake-analyst, dbt-engineer, neon-analyst, modal-ops, railway-ops, vercel-ops, code-reviewer, spec-reviewer |
plugin-hooks/ | 3 active + 1 opt-in | Auto-format on Write/Edit, pretooluse permission expansion, macOS notifications. (statusline.sh is opt-in — see SETUP_GUIDE §3.2.) Named plugin-hooks/ to avoid a Claude Code bug that deletes any project-root hooks/ directory between tool calls. |
Skills
Invocable as /claudna:<name> after marketplace install (e.g. /claudna:tech-debt). Bare names below are shown without the prefix for readability.
Workflow
| Skill | Description |
|---|---|
/session-resume | Pick up where you left off — scans git, PRs, plans, handoff notes |
/session-handoff | End-of-session capture — decisions, learnings, next steps |
/repo-health | Multi-repo dashboard — open PRs, CI status, stale branches |
/implement-plan | Execute a design doc or GitHub Issue — browse, pick, challenge, build, test, PR |
/worktree | Manage git worktrees for parallel Claude sessions |
/development-retro | Post-merge retrospective — systemic patterns, friction, breadcrumb trails |
/name-session | Label the current session so it shows up cleanly in /resume |
/weigh-development-paths | Compare multiple viable approaches at a development junction |
/adversarial-review | Structured plan challenge with evidence and anti-groupthink guards |
Code Quality
| Skill | Description |
|---|---|
/tech-debt | Scan for tech debt, generate phased remediation plans |
/security-audit | Scan 8 vulnerability categories, generate remediation plans |
/review-pr | Structured PR review with severity-categorized findings |
/review-changes | Review uncommitted changes for bugs, conventions, security |
/lessons | Capture and review lessons from corrections |
/verify-completion | Verify work is actually complete before claiming success |
/frontend-performance-audit | Trace re-render cascades, identify fetch/state/observer issues |
/access-path-audit | Audit cross-cutting concern consistency across system interfaces (API, CLI, MCP, Slack) |
/visual-crawl | Autonomous visual crawl — discover routes, screenshot at 3 viewports, file issues for findings |
Product
| Skill | Description |
|---|---|
/product-enhance | Discover enhancements via intent interviews and gap analysis |
/product-vision | Architecture-aware product vision — explore what the codebase could become |
/design-review | Visual audit at 3 breakpoints with phased fix plans |
/docs-review | Audit docs for accuracy, update plan statuses, archive stale docs |
/data-model-audit | Audit code-to-schema fit — traces code paths to DB, identifies mismatches |
Knowledge
| Skill | Description |
|---|---|
/learn | Ingest a document or repo into the shared knowledge store |
/reflect | Pre-compact synthesis — capture session context before it evaporates |
/index | Organize the shared knowledge store; regenerate INDEX.md |
/remember | Pull relevant prior knowledge at session start |
/publish | Distribute knowledge to other surfaces (bots, docs sites) |
Git
| Skill | Description |
|---|---|
/quick-commit | Stage all + commit with conventional commits format |
/commit-push-pr | Commit, push, and open a PR |
Data & Infrastructure
| Skill | Description |
|---|---|
/dbt | dbt build, test, compile, full-refresh |
/neon-query | Run SQL against Neon PostgreSQL via psql |
/neon-info | Neon dashboard — connection status, tables, branches |
/neon-branch | Create and manage Neon database branches |
Platform Operations
| Skill | Description |
|---|---|
/modal-status | Modal dashboard — apps, containers, secrets, GPU usage |
/modal-deploy | Deploy Modal apps with health verification |
/modal-logs | View and stream Modal app logs |
/railway-status | Railway dashboard — services, deployments, environments |
/railway-deploy | Deploy to Railway with build monitoring and rollback |
/railway-logs | Filter Railway logs by level, time, patterns |
/vercel-status | Vercel dashboard — deployments, domains, env vars |
/vercel-deploy | Deploy to Vercel with health verification and rollback |
/vercel-logs | Filter Vercel deployment logs |
/investigate-app | Platform-agnostic production debugging |
Utilities
| Skill | Description |
|---|---|
/notes | Persistent notes across sessions |
/find-skills | Discover and install new agent skills |
/heist | Raid a GitHub repo for skills, config patterns, and novel approaches |
/init-project | Set up CLAUDE.md, CHANGELOG.md, and .claude/ for a new or existing project |
/file-github-issue | File a GitHub issue from a screenshot + short description |
/github-activity-report | GitHub activity stats (PRs, commits, contributors) over a time window |
Daily Workflow
The skills form a pipeline:
Morning
───────────────────────────────────────────────────
/claudna:repo-health → See what needs attention across all repos
/claudna:session-resume → Pick a repo, get a 30-second briefing
Planning (when starting new work)
───────────────────────────────────────────────────
/claudna:tech-debt → Find what's broken → generates phase docs
/claudna:product-enhance → Find what could be better → generates phase docs
/claudna:product-vision → Explore what the codebase could become
Building (the core loop)
───────────────────────────────────────────────────
/claudna:implement-plan → Point at a phase doc
├── Challenge round (first principles review)
├── Build & test
├── PR with deliverable audit
└── Say "next" → auto-compacts → next phase
Reviewing
───────────────────────────────────────────────────
/claudna:review-pr 42 → Structured review of any PR
/claudna:review-changes → Audit uncommitted work
End of Day
───────────────────────────────────────────────────
/claudna:session-handoff → Capture decisions, learnings, next steps
→ Writes handoff file for tomorrow's /claudna:session-resume
First time? Start with /claudna:repo-health to see your repos, then /claudna:session-resume in any project.
Agents
Specialized personas invoked by skills or directly:
"Use snowflake-analyst to find the largest tables"
"Use dbt-engineer to review this model"
"Use neon-analyst to check table sizes"
"Use railway-ops to diagnose the deployment failure"
"Use vercel-ops to investigate the 500 errors"
"Use modal-ops to check GPU utilization"
Safety
The marketplace install is managed by Claude Code: plugins live under ~/.claude/plugins/cache/Claudfather/claudna/<version>/. Updates land in a new version directory; old versions are kept for ~7 days before auto-cleanup.
Never touched by claudna:
~/.claude/settings.json— user-managed. claudna never writes here. Recommended snippets are documented in SETUP_GUIDE for you to merge manually.~/.claude/notes/— personal data (lessons, decisions, patterns).
Project Template
project-template/ provides a starter .claude/ directory for individual projects. It's not shipped via the plugin — copy it manually or use /claudna:init-project:
| File | Purpose |
|---|---|
CLAUDE.md | Project instructions with workflow principles |
.claude/settings.json | Project-specific permissions |
.claude/lessons.md | Project-specific lessons from corrections |
Contributing
See CONTRIBUTING.md for the full guide. Writing a new skill? Start with the Skill Authoring Guide.
Quick version: branch off main, make your change, run python3 scripts/validate-skills.py, update CHANGELOG.md, open a PR.
Documentation
| File | Description |
|---|---|
| PROJECT_MISSION.md | What clauDNA is, what it's becoming, and where it fits in the Claudfather ecosystem |
| CLAUDE.md | Operating rules for agents extending clauDNA |
| SKILL_CONTRACT.md | The binding contract every skill must satisfy. Enforced in CI by scripts/validate-skills.py |
| SETUP_GUIDE.md | Deep-dive setup — settings.json bootstrap, headless/CI provisioning, Snowflake key-pair auth, troubleshooting |
| SKILL_AUTHORING_GUIDE.md | How to write, test, and submit a skill — patterns, examples, anti-patterns |
| CONTRIBUTING.md | Contribution workflow — bug reports, PRs, testing requirements |
| CLAUDE_MD_TEMPLATE.md | Template for project-level CLAUDE.md files (used by /claudna:init-project) |
| CHANGELOG.md | All notable changes |