Explore skills

Writes new worldbuilding content: civilizations, characters, locations, factions, events, languages, or narrative elements. Use when creating new entries, expanding existing ones, or when user says "create", "write", "add", "flesh out", "build", or "expand" for any non-science content. Does NOT write science files — use /writing-science for that.

Use this skill whenever the user wants to build, train, evaluate, or iterate on a supervised machine learning or deep learning model. Triggers include: any mention of training or fitting a model with labeled data, dataset preparation, hyperparameter tuning, cross-validation, model checkpointing, experiment tracking, overfitting, loss curves, metrics, or prediction visualization. Also trigger when

Product discovery framework based on Teresa Torres'' "Continuous Discovery Habits". Use this skill whenever the user is doing product discovery work — even if they do not explicitly say "OST," "Teresa Torres," or "discovery." Triggers include: (1) building, critiquing, or restructuring an opportunity solution tree, (2) identifying, organizing, or prioritizing customer opportunities, (3) designing

Run a pre-deploy browser audit of a live, preview, or local web page for accessibility, SEO, Lighthouse quality, and critical UX issues. Use when asked to audit a page/site before deployment, check WCAG 2.2 AA, WAI-ARIA, Lighthouse, accessibility, SEO, contrast, keyboard navigation, focus states, semantic HTML, forms, alt text, headings, ARIA attributes, best practices, or browser-visible web qual

Use this skill when creating, auditing, or redesigning a public GitHub repository so the repository is easy to understand, trust, share, install, and contribute to. Use together with github-repo-product-naming whenever naming, renaming, positioning, repo slug, About description, or product identity matters.

Maps a research paper or scientific concept onto the universe's physics, showing the chain from real principle to canon formalization. Use when incorporating a new finding, grounding a concept in real science, or when user says "integrate this paper", "map this onto our physics", "ground this concept", or "formalize this research". Does NOT search for papers — use /researching-papers for that.

Write, review, or rewrite user stories following Apprendere's agile practices guide. Use this skill whenever the user (or a subagent you spawn) is asked to draft, improve, refine, split, rewrite, or review user stories, convert functional requirements into stories, groom a backlog, translate a Confluence requirements page into stories, or create/update stories in Jira — even if they don't explicit

Audit a page for WCAG 2.1 AA accessibility issues. Traces the render chain, checks structural/semantic HTML, contrast indicators, ARIA, and outputs a prioritized report.

Interprets Agent Ninja routing recommendations injected via hooks. When you see [Agent Ninja] context in the conversation, follow the model/pattern/thinking recommendations. Use when routing decisions appear in context, when deciding which model to use, or when considering subagents vs direct execution.

Writes new science files following academic prose standards: third-person voice, present tense for laws, in-universe terminology, consistent equation formatting, citation format. Use when creating new physics, chemistry, biology, or science files, expanding existing science content, or when user says "write", "create", "draft", "formalize", or "derive" in a science context. Does NOT write civiliza

Write, review, or rewrite Acceptance Criteria for user stories. Use this skill whenever the user (or a subagent you spawn) is asked to draft, improve, refine, rewrite, or review acceptance criteria, turn a user story into AC, translate behavior specs into Given/When/Then, critique existing Gherkin scenarios, define the "definition of done" for a story, or expand on a story's expected behavior — ev

Product management framework based on Melissa Perri''s "Escaping the Build Trap". Use this skill whenever the user is discussing product strategy, roadmap construction, product team maturity, or symptoms of feature-factory behavior — even if they do not explicitly say "build trap" or "outcome-driven." Triggers include: (1) diagnosing whether a team is stuck shipping features without measuring outc