← all publishers

clay-good

@clay-good source repo

Report this profile Claim this profile

• 20 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Anvilate · clay-good

   Screen a mechanical or structural part against cited engineering checks with Anvilate, and report the result the way an engineer would. Use when asked to size, check, or validate a part, joint, member, or vessel, or to interpret an Anvilate scorecard.
   0
   installs
2. ▌
   Tester · clay-good

   Test runner and fixer. Spawns to run the full test suite, diagnose failures, and fix them.
   0
   installs
3. ▌
   Builder · clay-good

   Code implementation specialist. Spawns to implement a specific feature, module, or function.
   0
   installs
4. ▌
   Explorer · clay-good

   Codebase exploration and analysis specialist. Fast research before implementation.
   0
   installs
5. ▌
   Reviewer · clay-good

   Security and code quality reviewer. Read-only deep review for vulnerabilities and quality issues.
   0
   installs
6. ▌
   Lint Fix · clay-good

   Run the project linter and formatter, fix all violations.
   0
   installs
7. ▌
   Run Tests · clay-good

   Run the full test suite, diagnose any failures, fix them, and re-run until green.
   0
   installs
8. ▌
   Verify All · clay-good

   Run all quality checks — tests, lint, format, security scan.
   0
   installs
9. ▌
   Update State · clay-good

   Update .codelicious/STATE.md with accurate current status.
   0
   installs
10. ▌
    Openlore Debug · clay-good

    Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
    0
    installs
11. ▌
    Openlore Orient · clay-good bundle

    Retrieve relevant functions, callers, spec sections, and insertion points from OpenLore before reading source files. Use when starting work that needs structural orientation in an existing codebase.
    0
    installs
12. ▌
    Openlore Repair · clay-good

    Reconcile one existing OpenSpec specification from deterministic OpenLore MCP observations. Use when a spec may be incomplete, stale, partially covered, or orphaned from current code.
    0
    installs
13. ▌
    Openlore Generate · clay-good

    Author a new OpenSpec domain specification from deterministic OpenLore MCP evidence. Use when asked to reverse-engineer, generate, or document a specification for existing code.
    0
    installs
14. ▌
    Openlore Brainstorm · clay-good

    Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
    0
    installs
15. ▌
    Openlore Write Tests · clay-good

    Write and run real tests for a function or spec scenario after reading implementation and contract evidence. Use when asked to add, improve, or repair tests without stubs or placeholders.
    0
    installs
16. ▌
    Openlore Plan Refactor · clay-good

    Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
    0
    installs
17. ▌
    Openlore Review Changes · clay-good

    Review code changes using OpenLore risk, call, coverage, and cluster evidence without editing code. Use when asked for a change review, pre-PR safety check, or merge recommendation.
    0
    installs
18. ▌
    Openlore Implement Story · clay-good

    Implement a brownfield story with OpenLore orientation, risk checks, spec validation, tests, and drift detection. Use when asked to implement or continue a story in an existing codebase.
    0
    installs
19. ▌
    Openlore Analyze Codebase · clay-good

    Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
    0
    installs
20. ▌
    Openlore Execute Refactor · clay-good

    Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
    0
    installs