Results for “story”

Embody the voice and comedy methodology of Jo Koy, using his signature techniques and cultural insights to craft humorous, family-centric stories and presentations.

Adopts the voice and methodology of comedian Elaine May to provide creative writing and improvisation guidance, emphasizing character-driven comedy and emotional truth.

Trigger: press release, PM memo, PRD memo, product launch narrative, launch story. Scope: Writing press releases and future launch stories for project alignment. Boundary: Excludes writing functional code or task tracking.

Provides creative advice in the style of director Tsui Hark, offering visual, narrative, and scene design suggestions for filmmaking and storytelling.

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

This skill should be used when implementing features from a PRD spec, tracking implementation progress, or resuming work across sessions. Covers Dex task management for PRD story execution, daily workflows, and skill auto-loading.

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

Configures and troubleshoots Copado Essentials deployment pipelines in Salesforce, covering user stories, branches, promotion paths, conflict resolution, and deployment modes.

Builds and governs design systems with a three-layer token architecture, component specs, and design-to-code handoff, including slide generation.

Turn account data into a QBR that earns the renewal. It builds the value-delivered story, adoption against the goals they signed up for, the open risks stated plainly, the forward roadmap, and the expansion ask, then hands you a deck outline. Built for B2B customer success teams, customizable to your CRM and product analytics. Trigger on "build a QBR", "prep the business review", "quarterly review for this account", "what do I show the customer", "value story for the renewal", or any account-review prep.

Generate a serial, multi-chapter narrative digest of a project's claude-mem history, producing one digest per ISO week with coherent story flow across chapters.

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.

Headless CMS integration guidance — Sanity (native Vercel Marketplace), Contentful, DatoCMS, Storyblok, and Builder.io. Covers studio setup, content modeling, preview mode, revalidation webhooks, and Visual Editing. Use when building content-driven sites with a headless CMS on Vercel.

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.

Collaboratively write multi-volume novels with structured commands for outlining, planning, drafting, writing, health-checking, and archiving, while maintaining world-building consistency across chapters.

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.

Writes or updates pathway pages for Alan Hirsch's platform, following a 12-section architecture that grounds frameworks in Scripture and story, offers practices, and invites course-based formation.

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.

Provides end-to-end job search support through five specialized agents: story mining, job recommendation, resume optimization, mock interviews, and skill gap analysis, with scripts to generate resume files in multiple formats.

Analyzes and recreates Wired magazine's editorial design language: a strict black-and-white duet, proprietary serif/sans typographic system, square buttons, magazine-style story grid, and hairline borders.

Knowledge base from "Contagious: Why Things Catch On" by Jonah Berger. Use when applying Berger's STEPPS framework for word of mouth, virality, social currency, triggers, emotion, social proof, practical value, and storytelling, studying the book, or referencing its concepts.

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.

User-story-driven test coverage audit and plan — no test writing in this pass. Use when "test coverage plan", "coverage audit", "traceability matrix", "fake-green tests", "uncovered user stories", "plan tests for critical flows", or "whats not tested". Mutation score / assertion theater → test-mutation.

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.

Full end-to-end Mushi Mushi integration smoke test: bug capture → AI triage → story mapping → TDD test generation → approval → execution → PDCA cycle. Use when "test mushi integration", "verify full pipeline", "mushi e2e check", "does mushi work end-to-end", "smoke test mushi", or after deploying changes.

Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.

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.

Turn raw ideas into one clear pre-planning concept artifact by choosing the right framing mode: problem framing, audience and value framing, concept shaping, game concept framing, or story packaging. Use when the user needs the next artifact before PRDs, sprint plans, launch execution, or game-production routing.

Framework-driven copywriting for ads, landing pages, emails, sales pages, and CTAs. Includes AIDA, PAS, BAB, 4Ps, StoryBrand, QUEST, FAB, and more. Use when writing conversion-focused copy, ad creative, headlines, email sequences, sales pages, or when the user mentions copywriting frameworks, persuasive writing, or direct response copy.

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

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.

Documents Replicate's design system: warm cream canvas, hot orange accent, three-family typography stack (rb-freigeist-neue, basier-square, JetBrains Mono), fully rounded interactive elements, and a section rhythm that alternates between cream, orange hero, dark code-story, and black footer.