localstack

Author one loop-harness planning ticket in the format the implement-ticket loop consumes. Use when asked to plan a feature, scope a change, draft a ticket, or turn a described problem into a ticket the loop can run. Writes one ticket file to the configured plans directory.

Run one planning ticket through the loop lifecycle - perceive (ledger + git reconcile), implement tests-first, gate via `loopctl stamp`, self-review, adversarial review, commit, close via `loopctl finish`. Use when asked to implement the next ticket, run the loop, or continue autonomous ticket implementation.

Generate static artwork/illustrations for a repo with Nano Banana Pro (aka "nano banana", Gemini 3 Pro Image) via the bundled generate_art.py — craft a detailed prompt, run the script, view the result, iterate. Use this whenever the user wants to create, generate, or regenerate a visual asset for a project: an architecture diagram, portrait, card/illustration, icon, splash, or any image that lands as a PNG in the repo — even if they don't name the tool or just say "make me an image / a picture of X". Do NOT trigger for application runtime image needs, or for editing source code rather than producing an image file.

Remove a solid background from an image and write a transparent PNG, using the bundled remove_background.py. Use this whenever the user wants to knock out, drop, or make transparent the background of a logo, banner, icon, or other static image asset in a repo, or to trim an asset to its content and pad it. Pairs with generate-art: generate a flat asset, then key its background here. Do NOT trigger for photo cutouts needing subject segmentation, for runtime image processing, or for editing source code rather than an image file.

Teach the user a new codebase, technology, framework, or system by walking through it from high-level architecture down to implementation details using a paginated, layered approach. Use this skill whenever the user wants to understand how something works, needs onboarding onto a new technology, asks you to explain a system end-to-end, or says things like "walk me through", "explain how X works", "I need to learn X", "teach me", or "help me understand". Also use when the user shares documentation and asks to be taught from it.

Write or refactor project documentation — tutorials, how-to guides, reference pages, and explanation articles — using the Diátaxis framework. Enforces strict mode purity (a tutorial is not a how-to is not a reference is not an explanation), Orwell's six rules for clear prose, and a ladder-of-abstraction rhythm where concrete examples open and close each piece. Targets HUMAN readers — not agents — so emphasizes plain, everyday English over jargon. Use whenever the user asks to write, draft, refactor, edit, improve, or polish documentation — phrases like "write a tutorial", "draft a how-to", "turn this into a reference", "document this feature", "rewrite this doc", "improve the README", "add user docs", "document the API", "explain how X works for newcomers", or any task that produces user-facing prose for a software project. Triggers even when the user does not say "Diátaxis" explicitly — any doc-writing or doc-refactoring task gets this lens.

Create and maintain a MANIFESTO.md at a project's root — a living document capturing the project's vision, architecture, architectural rules, and design rules, where every hard "invariant" is anchored to the code that enforces it. Use this whenever the user wants to "write/set up a manifesto", "document the architecture and design rules", "create a vision/design doc", "capture our architectural invariants", or asks how a project is *supposed* to be built. ALSO use it proactively to keep the doc honest: whenever the user makes or describes an architecturally significant change — a new module or package, a changed/added invariant, a refactor of a core boundary, a dependency added or removed, a schema change — offer to reconcile MANIFESTO.md, even if they don't mention the manifesto. Three modes: init (interactive Q&A + codebase mining to bootstrap the doc), sync (reconcile the doc with changed code), and verify (read-only audit that every enforcer still resolves).

Review code for architectural quality, design principles, and language-specific best practices. Works top-down: starts with system architecture and abstraction boundaries, then moves to design principles (SOLID, coupling, cohesion), then to language-level patterns and anti-patterns. Supports any language but has deep Python expertise (typing, async, protocols, testing). Use this skill whenever the user asks to review code, says "review this", "review my PR", "what's wrong with this code", "code review", "check my code quality", "how can I improve this", "python review", "/python-review", or wants feedback on code quality, architecture, or design. Also use when the user pastes code and asks for opinions or improvements.

Generate or rewrite project READMEs that are instantly clear, trustworthy, and beautiful. Use whenever the user asks for a README, project documentation, repo overview, onboarding guide, getting-started instructions, or says anything like "make my readme nice", "document this project", "write a readme", or "explain what this does". Triggers on README, readme, documentation, project summary, onboarding, getting started.

Release a new version of a project. Handles version bumping (alpha / release candidate / stable), tagging, pushing, creating a GitHub release with curated release notes, and monitoring the CI pipeline until success. Use whenever the user says "release", "new version", "tag a release", "bump version", "ship it", "cut a release", "cut an RC", "promote RC", or anything about creating a new project version/tag.

Daily engineering blog scraper — visits top AI/eng blogs, extracts new articles verbatim, stores in Memex

Receives issue reports, deduplicates them, and maintains structured post-mortem notes in the Memex inbox vault

Connects recent Memex insights to GitHub projects by opening issues or PRs with actionable suggestions

Produce a structured, retrievable daily reflection over the last 24h of Memex activity. Persistence is mandatory — the reflection note must exist every day, even when delivery is silent.

Autonomous intelligence monitor -- continuous web monitoring, change detection, knowledge graph updates, and event alerts

Receives Medium digest emails, filters clickbait, and captures worthy articles verbatim to Memex inbox via archive sources

Autonomous deep researcher -- exhaustive investigation, cross-referencing, fact-checking, and structured reports