Results for “story”

Expert in narrative theory, story structure, character arcs, and literary analysis — grounds advice in established frameworks from Propp to Campbell to modern narratology

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

Record polished UI demo videos using Playwright with visible cursor, natural pacing, and storytelling flow.

Analyzing session replays, extracting persona-based behavioral patterns, and storytelling UX issues. Reads the 'why' from real user operation logs. Works with Field/Echo for persona validation.

Scaffold Next.js/React projects, generate components, analyze bundle sizes, and apply React/Next.js optimization patterns.

Chains /mvp and /backend-spec to analyze an app from video, screenshots, or description, then generate implementation stories from the analysis.

Transforms git diffs and change descriptions into narrative commit messages that explain why a change was made, following Conventional Commits format.

Automate project management workflows in Shortcut -- create stories, manage tasks, track epics, and organize workflows through natural language commands.

Create clear, effective data visualizations with chart selection, color theory, and annotation best practices using the inference.sh CLI.

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

Review UI implementations against design quality standards and design system compliance, or create distinctive, production-grade frontend interfaces from scratch.

Use to lock the single narrative arc before drafting — converts a set of correct results into one Cell-shaped story that runs hypothesis → mechanism → significance, not a list of experiments.

Create animated technical explainers using Manim for graphs, workflows, system diagrams, and product walkthroughs with precise motion and clear scene planning.

Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed.

Create user stories using Mike Cohn format with Gherkin acceptance criteria, translating user needs into development-ready work with clear outcomes and testable conditions.

Use to write Cell's Summary — a single unstructured paragraph of ≤ ~150 words that conveys the complete story, the mechanism, and the broad significance, quantified and readable by a general life-scientist. Late-stage polish.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday.

Renders a story, question, or meme as a realistic Reddit post card with vote rail, comments, and awards, suitable for video overlays or social media sharing.

Close the PDCA loop on this session's diff. Headed playwright-cli, fix as you go. Use when "test my changes", "PDCA this". Pixel diffs → test-visual-regression. Story CRUD → test-qa. Monkey / guest vs logged-in → test-exploratory.

Turn "we should get press" into an earned-media plan a journalist might actually answer. The story angle worth their byline, a target list by beat, a pitch built for one reporter at a time, and a follow-up rhythm that is persistent without being a pest. Built for B2B teams doing their own PR, customizable to your story and your beats. Trigger on "help me pitch this", "build a PR plan", "which journalists cover this", "write a media pitch", "how do I follow up with press", or any earned-media outreach question.

Load this skill when the user says "implement issue", "implement-issue", or "/implement-issue". Implements a GitHub story issue end-to-end: prepares base branch, creates feature branch, implements the requirements, verifies via the verify-implementation skill, and opens a PR.

Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.

Load this skill when the user says "close issue", "close-issue", or "/close-issue". Verifies IT and UC acceptance criteria for a story issue, ticks off passing checkboxes, and closes the issue only if all criteria pass and the linked PR has been merged.

Unity / UEFN / Fortnite person pack for Content Factory. Use when the user says person unity, @person-unity, Unity person, UEFN person, Fortnite map person, or HY-World person. Auto-loads unity-expert persona plus cf-hyworld-fortnite, image-generation, and storyboarding.

This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture", "world history", "technology system", "religion", "economy", or wants to develop any aspect of a story's world and setting.

Run a co-sell with a partner on a named account and actually close together, not just trade a lead. It maps the account across both companies, sets who owns what so nothing falls between you, builds the joint value story neither of you tells alone, and plans the path to close so the partner is a force in the deal, not a spectator. Built for B2B partnerships and sales teams, customizable to your CRM and your co-sell motion. Trigger on "run a co-sell", "co-sell on this account", "map the account with our partner", "who owns what in this joint deal", "joint value story", or any partner co-sell request on a named account.

Exploratory ("monkey") QA of a live app as GUEST then LOGGED-IN, then diff. Headed playwright-cli, junk inputs, nav abuse. Use when "monkey test the app", "exploratory QA", "wander like a confused user", or "guest vs logged in". Story CRUD → test-qa. Hostile sweep → test-red-team. This-diff PDCA → test-playwright.

Use when triaging a study before any writing — stress-tests whether it clears Cell's bar (a complete, mechanistic, hypothesis-driven story with multiple converging lines of evidence) or belongs at a sibling. Use this first to decide Cell vs Molecular Cell vs Cell Reports vs Cell Reports Medicine before investing in framing or figures.

Create or update a MoonSpec feature specification from a natural language feature request or referenced declarative design. Use when the user asks to run or reproduce `/moonspec.specify`, create a `spec.md`, initialize a feature directory under `specs/`, preserve the original feature request for later verification, map source design requirements, or generate a single-story MoonSpec specification with a requirements quality checklist.

Craft messages that are understood, remembered, and drive action using the SUCCESs checklist (Simple, Unexpected, Concrete, Credible, Emotional, Stories). Use when the user mentions "make it memorable", "sticky messaging", "tagline", "value proposition", "why the message isnt landing", "knowledge curse", "surprise gap", or "concrete language". Also trigger when writing pitch decks, simplifying complex product explanations, or making presentations more compelling and memorable. For narrative brand frameworks, see storybrand-messaging. For viral sharing, see contagious.

Use to distil a CX dashboard into the three numbers a board or exec actually needs — volume/demand health, quality/outcome, and cost/efficiency — with commentary that drives decisions instead of forty tiles nobody acts on. Trigger for "board pack", "exec summary for support", "what should leadership see", "too many metrics on the dashboard", "three KPIs for the board", quarterly business review CX section, or when a leadership deck is mostly charts with no story.

Expert social media writing skill for creators, professionals, and brands who want to write posts that actually perform. Use this skill whenever the user wants to write, improve, or get help with any social media content — including LinkedIn posts, Twitter/X tweets or threads, Instagram captions, or TikTok captions. Also trigger for: "write a post about", "help me with my LinkedIn", "draft a tweet", "create a thread", "write a caption", "I want to post about", "turn this into a social post", "make this more engaging", or any request to create or improve content for a social platform. Do NOT limit to obvious requests — if the user has an idea, a story, or a piece of content and mentions a platform, use this skill.

Write the context brief a first-time tester gets before testing an app, tool, codebase, or product — it explains WHAT the thing is and why it exists, while deliberately withholding HOW anything works. The companion to the fresh-eyes skill; the brief it produces is the "starting information" handed to a fresh-eyes tester. Use this whenever the user is preparing a fresh-eyes or first-time-user test and needs the setup material, or says things like "describe my app without giving anything away", "write the context card for the tester", "explain what it is but not how to use it", "set up the newcomer test", "what would the tester be told going in?", or wants a spoiler-free description of their product. Also use it when someone asks for the briefing/intro that a new tester, new hire, or evaluator should receive before first contact with the thing being tested.