← all publishers

jmmarotta

@jmmarotta source repo

Report this profile Claim this profile

• 11 skills
• 0 followers
• 1 week ago last updated

1. ▌
   Web Access · jmmarotta bundle

   Use for any web access - searching for authoritative external docs, current information, release notes, pricing, or news, AND fetching or extracting content from a specific URL. Routes both through codex so raw page content stays out of the parent context.
   1 install
2. ▌
   Code Review · jmmarotta

   Review diffs, commits, or pull requests for correctness, regressions, integration risk, and design quality. Load `software-design` for design judgment, `software-implementation` for code shape or verification depth, and `software-planning` only when planning artifacts matter.
   1 install
3. ▌
   Go Practices · jmmarotta bundle

   Use for writing, reviewing, refactoring, or structuring Go code with curated Go practices and guidance around simplicity, readability, naming, package design, API design, error handling, concurrency, and testing. Current references are centered on Dave Cheney's Practical Go recommendations.
   1 install
4. ▌
   Skill Creator · jmmarotta bundle

   Guide for creating effective skills. Use when creating, updating, restructuring, or validating a skill package with specialized workflows, knowledge, tool integrations, or bundled resources. Use `agent-instruction-writing` when editing the instruction text itself.
   1 install
5. ▌
   Repo Bootstrap · jmmarotta bundle

   Use for new-repo bootstrap or whole-repo rebaseline, especially when choosing topology, dependency policy, baseline tooling, `AGENTS.md`, and verification strategy.
   1 install
6. ▌
   Bonsai Subagent · jmmarotta

   Spawn subagents with the bonsai coding-agent CLI when no task tool or native subagent is available. Use for self-contained exploration, research, review, parallel investigations, or isolated work that would bloat the parent context.
   1 install
7. ▌
   Frontend Design · jmmarotta bundle

   Create distinctive, production-grade web UI. Use for web components, pages, apps, posters, landing pages, dashboards, React components, HTML/CSS layouts, or styling and beautifying existing web interfaces.
   1 install
8. ▌
   Software Design · jmmarotta

   Apply A Philosophy of Software Design when evaluating or shaping APIs, module boundaries, abstractions, invariants, information hiding, and complexity tradeoffs.
   1 install
9. ▌
   Software Planning · jmmarotta

   Plan non-trivial software changes before coding. Use for requirements framing, approach selection, API or module design, spec writing, verification planning, and rollout or rollback planning.
   1 install
10. ▌
    Software Implementation · jmmarotta

    Implement planned software changes with local verification loops. Use after a plan or spec exists, or for debugging, behavior-preserving cleanup, and contained non-trivial edits that do not reopen design work.
    1 install
11. ▌
    Agent Instruction Writing · jmmarotta

    Use when editing `AGENTS.md`, `SKILL.md`, or agent system prompts.
    1 install