Pattyboi101

Sector pack for academic research and lit-review work. Personas for literature review, methods design, data extraction, academic writing, citations, and peer review.

Academic research workflows.

Academic research workflows.

Academic research workflows and literature review.

An example persona. Replace this description with what this persona actually does (≤ 200 chars).

A starter template for authoring your own spore. Replace this description with your sector's purpose.

Interviews the user about a new sector, drafts the directory + manifest + persona scaffolding into ~/.myceliate/skills/<name>/.

Meta-spore for Myceliate itself. Used to author new spores. The spore-creator persona walks the user through interview-style spore authoring.

Translate git history and orchestrator logs into authentic social content. Use when turning recent technical work into tweets, Dev.to posts, or changelog entries without manual summarisation.

Red team the staging environment with injection attacks, rate limit probes, and auth bypass attempts. Use before major releases or when adding new user-input surfaces.

Deploy Your Project to production safely. Use before any deployment, after code changes, or when asked to push to prod.

Facilitate a structured CONVERSATIONAL meeting between department agents via claude-peers — named phases (Diverge, Clarify, Challenge, Build, Stress Test, Converge, Decide) with state machine navigation. Agents push back on each other and build on each other's ideas. Minimum path: Diverge → Challenge → Build → Stress Test. Early exit only after Stress Test. NOT for simple task dispatch (use orchestra-management). NOT for solo research (use rd-architect).

Manage the 6-department orchestra via claude-peers. Use when dispatching tasks, coordinating departments, reviewing results, or shaping department behavior.

Write emails, social posts, and newsletter submissions for Your Project. Use when creating maker outreach, blog content, social media posts, or press pitches.

Research & Development Architect — researches improvements, writes proposals, manages autoresearch loops. Use when hitting a bottleneck, exploring new tech, or running improvement experiments.

Audit LLM token usage across departments, identify waste, and recommend model/caching optimisations. Use when costs are rising or before scaling the orchestra.

Fact-check an email from Ed against the IndieStack codebase for hallucinations

Frontend UI polish and design tokens enforcing IndieStack styling

Facilitate a structured CONVERSATIONAL meeting between Patrick and all orchestra agents — named phases (Diverge → Challenge → Build → Stress Test) with state machine navigation. Agents push back on each other, build on each other's ideas, and the chair navigates phases autonomously. Early exit only after Stress Test completes.

Audit your current project for token-saving opportunities by finding IndieStack tools that replace code you'd write from scratch

Build a complete open-book exam binder (vault + per-lecture .docx + cross-reference validation) for a course, using your agent's own LLM session — no separate API key. Triggers - `/build-binder <course-path>`, "build the binder for <course>", "process my lectures into a binder". For an already-extracted course, the skill is incremental — it skips unchanged sources.

Scaffold a new open-book-exam-prep course folder for the user. Triggers - "set me up an open-book course", "create a course for X", "scaffold a course", `/setup-course <name>`. Reads from any lecture sources the user points at and produces a complete course/ directory with course.yaml, sources/, templates/ overrides if needed, ready for `python -m pipeline.run --course <path>`.

Generate or mark mock open-book exam papers from a course's binder. Triggers - `/practice-paper <course-path> <module-code>` to generate; "mark it" / "ready to mark" / "grade this" / `/practice-paper <course-path> mark <paper-path>` to mark. If the user is already inside a course directory (CWD has course.yaml), the course-path arg can be omitted.

Analyze project dependency health before installing or upgrading packages