DojoGenesis
- 443 skills
- 0 followers
- 17 hours ago last updated
- ▌
- ▌
- ▌ Create Worktree Skill · dojogenesisUse when the user explicitly asks for a SKILL to create a worktree. If the user does not mention "skill" or explicitly request skill invocation, do NOT trigger this. Only use when user says things like "use a skill to create a worktree" or "invoke the worktree skill". Creates isolated git worktrees with parallel-running configuration.
- ▌ Idempotent Redundancy · dojogenesisEnsure fallback and redundancy paths are idempotent to prevent loops, churn, or data corruption. Use when adding belt-and-suspenders patterns. Trigger phrases: "make fallback safe", "idempotent retry", "safe redundancy pattern".
- ▌
- ▌
- ▌
- ▌
- ▌ Tldr Code Analysis · dojogenesis5-layer code analysis (AST, Call Graph, CFG, DFG, PDG) that yields 95% token savings over raw file reads. Use when: 'systematically understand an unfamiliar codebase', 'analyze code structure with minimal tokens', 'map call graphs and data flow', 'find dead code and architectural layers', 'trace variable definitions across files'.
- ▌
- ▌
- ▌
- ▌
- ▌ Background Agent Pings · dojogenesisTrust system reminders as agent progress notifications instead of polling for completion. Use when waiting on background agents. Trigger phrases: "agent still running", "check agent progress", "stop polling agents".
- ▌
- ▌
- ▌
- ▌ Email Template Builder · dojogenesisBuild transactional email systems with React Email/MJML templates, provider integration, i18n, and dark mode. Use when implementing email notifications. Trigger phrases: "build email template", "transactional email", "email provider setup".
- ▌
- ▌ Observe Before Editing · dojogenesisCheck actual system outputs before editing code to fix bugs -- outputs don't lie, assumptions do. Use when debugging unexpected behavior. Trigger phrases: "check before editing", "verify actual output", "don't assume the error".
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Community Claude Md Guardian · dojogenesisAudits CLAUDE.md files for conflicts, stale rules, missing sections, and cross-file coherence. Produces a health report with auto-fix suggestions — audit only, no enforcement mechanism. Full version (adds a PreToolUse hook to enforce the ruleset going forward): `system-health:claude-md-guardian`. Use when: 'check claude.md', 'audit CLAUDE.md', 'fix claude.md', 'claude md health'.
- ▌
- ▌ Adversarial Reviewer · dojogenesisAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
- ▌
- ▌
- ▌ Audit Sweep Dispatch · dojogenesisRoutes health-audit findings to the correct execution path — main thread, foreground fix, or parallel agent waves. Use when health-audit findings need to be sorted by effort and dispatched as agent waves.
- ▌
- ▌
- ▌ Agent Context Isolation · dojogenesisPrevent sub-agent output from polluting the main context window using background execution and file-based results. Use when agent transcripts bloat context. Trigger phrases: "isolate agent context", "context window bloat", "agent output too large".
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Qlty During Development · dojogenesisRun QLTY lint and format checks during development to catch issues early, not just before commit. Use after significant code changes. Trigger phrases: "run linter", "check code quality", "format before commit".
- ▌
- ▌
- ▌ Maestro Orchestration · dojogenesisConductor agent pattern that decomposes complex tasks, dispatches specialist sub-agents, manages dependencies, and synthesizes results into a unified deliverable. One specific orchestration pattern — a single conductor coordinating specialists. Use directly when that shape already fits; use `orchestration-pattern-selector` first if unsure, or `agent-dispatch-playbook` to plan a general parallel dispatch's mechanics. Use when: 'coordinate multiple specialist agents', 'orchestrate a complex multi-phase task', 'run a conductor pattern across agents', 'this task needs live agent coordination', 'decompose and dispatch to sub-agents'.
- ▌
- ▌
- ▌ Parallel Agent Contracts · dojogenesisPrevent type duplication across parallel agents by requiring grep-before-create and tsc verification. Use when launching parallel code implementation agents. Trigger phrases: "parallel type conflicts", "duplicate interface", "agent type contract".
- ▌
- ▌
- ▌
- ▌ Router First Architecture · dojogenesisEnforces routing through domain routers before invoking individual tools, abstracting tool selection into deterministic intent-to-command mappings. Use when: 'set up domain router', 'router-first pattern', 'route before calling tool', 'co-activate with router', 'deterministic skill routing'.
- ▌
- ▌
- ▌
- ▌
- ▌ Session Lifecycle Automation · dojogenesisDesigns and configures all three loops of solo-operator session automation — session bookends, background maintenance agents, and a delegation flywheel. Use when setting up a new workspace, recovering from the 44% zero-artifact session leak, or preparing to scale delegation across multiple concurrent agents.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Contract And Proposal Writer · dojogenesisGenerates professional, jurisdiction-aware business documents — freelance contracts, project proposals, SOWs, NDAs, MSAs — in Markdown with docx conversion instructions. Use when: 'write a contract', 'draft proposal', 'create SOW', 'NDA template', 'MSA', 'freelance agreement', 'project contract'.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Parallel Tracks · dojogenesisProduces a parallel-tracks execution plan with phased structure, self-contained track specifications, integration contracts, and a mandatory wiring gate. Plans the split before any agent runs — the spec-side artifact. To actually dispatch and verify the agents once tracks are planned, use `agent-orchestration:parallel-dispatch`. Use when 'split into parallel tracks', 'organize these tracks into phases', or 'plan parallel development for this release'.
- ▌
- ▌
- ▌ Orchestration Pattern Selector · dojogenesisSelects the correct multi-agent orchestration pattern for a task using an 11-signal selection matrix. Use this first, upstream of `agent-dispatch-playbook` (which plans dispatch mechanics once the shape is known) and `maestro-orchestration` (one specific pattern this skill might select). Use when choosing which orchestration pattern fits a multi-agent task.
- ▌ Context Ingestion · dojogenesisProduces a phased, file-grounded action plan from 1-2 uploaded documents (specs, meeting notes, design docs, or code files) with concrete deliverables and binary success criteria per phase. Use when: 'create a plan from this spec', 'plan the refactoring from these files', 'what are the next steps from these docs'.
- ▌ Gap Audit Then Fix · dojogenesisSpec-to-fix pipeline: audit a codebase against its specification, classify gaps by severity, fix in parallel, track in GAPS.md registry. Use when a spec exists but implementation completeness is unknown.
- ▌ Planning With Files · dojogenesisProduces a routing decision and delegated output by analyzing uploaded files and user intent, then dispatching to the correct specialized skill (context-ingestion, research-synthesis, or release-specification). Use when: 'create a plan from these files', 'synthesize these papers', 'what should I do with these uploads', 'not sure which skill to use but I have files'.
- ▌ Specification Writer · dojogenesis bundleProduces a format-calibrated specification document — Full (5,000-15,000 words, all sections), Lean (1,000-3,000 words, agent-ready), or Minimal (delta + code examples) — matched to the scope and audience of the request. Use when: 'write a spec for this feature', 'spec out this release', 'design the architecture for X', 'document this for the implementation agent'.
- ▌ Frontend From Backend · dojogenesisProduces a backend-grounded frontend specification document covering API contracts, integration guide, auth flows, and updated track prompts. Use when 'spec the frontend for this API', 'write frontend spec from backend', or 'ground the UI in this existing backend'.
- ▌ Implementation Prompt · dojogenesisProduces a self-contained implementation prompt document with objective, context grounding, numbered requirements, file manifest, binary success criteria, constraints, and backend grounding — ready for autonomous agent execution. Use when 'write an implementation prompt', 'commission this spec', or 'convert spec to prompt'.
- ▌ Release Specification · dojogenesisProduces a production-ready release specification document (Full or Lean format) including current-state audit, technical architecture with code examples, implementation plan, and risk assessment. Use when 'write a release spec', 'create a release specification for vX.X.X', or 'ground this spec in the codebase'.
- ▌ Zenflow Prompt Writer · dojogenesisProduces a structured Zenflow commission document (Objective, Context & Grounding with pattern files, step-by-step Requirements, File Manifest, binary Success Criteria, and explicit Constraints) from a finalized spec, saved to prompts/vX.X.X/. Use when: 'write a Zenflow prompt', 'commission Zenflow for this spec', 'turn this spec into a Zenflow prompt', 'create the implementation prompt for Zenflow'.
- ▌ Codebase Audit Grounding · dojogenesisProduces a quantified current-state report (test count, aria markers, error boundaries, storage usage, dependencies) used to anchor specifications in measured reality rather than assumptions. Use when: 'audit the codebase before speccing', 'ground this spec in reality', 'what does the code actually look like', 'measure before I write the spec'.
- ▌ Pre Commission Alignment · dojogenesisProduces a gap inventory and Track 0 remediation commit that closes mismatches between implementation prompts and actual codebase state, ensuring parallel tracks start from a clean, type-safe foundation. Use when: 'commission these tracks', 'run Track 0 before handing off', 'check for spec-to-code drift', 'align before we build'.
- ▌ Pre Implementation Checklist · dojogenesisProduces a completed pre-implementation checklist appended to a specification document, confirming vision clarity, technical readiness, implementation plan completeness, and Track 0 codebase alignment before any agent is commissioned. Use when: 'verify the spec is ready', 'run the pre-commission check', 'is this spec ready to hand off', 'gate this before we commission'.
- ▌ Spec Constellation To Prompt Suite · dojogenesisProduces a suite of coordinated, self-contained implementation prompts and a master integration contract table from a set of interconnected specs. Use when 'convert specs to prompts', 'ready to commission these specs', or 'coordinate these parallel tracks into executable prompts'.
- ▌ Bring · dojogenesisSurface and stage TODAY'S ONE outward action (send/decision/close/ship) from the project's bring/ queue, then log the outcome on the human's word. Use when the user says "bring it", "what's my bring", "log the send", "skip today's bring", or when the SessionStart brief shows an unbrought action and the user engages with it.
- ▌ Mvp · dojogenesisYou are a business advisor channeling the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Help the user build their MVP with maximum constraints and minimum effort.
- ▌
- ▌
- ▌
- ▌ Adr Writer · dojogenesisProduces a numbered Architecture Decision Record with context analysis, route comparison, decision rationale, consequences, and propagation checklist. Use when: 'write an ADR', 'architectural decision', 'record a decision', 'ADR for'.
- ▌ Bring Setup · dojogenesisInitialize the bring loop in the current project — scaffold bring/actions.md + ledger, seed the first real outward actions from conversation, and explain the daily contract. Use when the user says "set up bring-loop", "install the bring loop", "start gating my sends", or asks how to get the BringItCruz effect in their system.
- ▌
- ▌ Hooks · dojogenesisWrite Claude Code hooks using shell wrappers that pipe to TypeScript handlers via npx tsx. Use when developing PreToolUse or PostToolUse hooks. Trigger phrases: "create hook", "hook development", "shell to TypeScript handler".
- ▌
- ▌
- ▌
- ▌