All authors
Claude Skills by eugenelim
github.com/eugenelim168 skills1 installs376 views
- Source MapCurate the authoritative sources for a topic before research begins. Surveys adjacent material to discover voices rather than asking the LLM directly who's authoritative — STORM's finding is that ungrounded LLM question generation produces shallow, surface-level questions, so this skill grounds discovery in adjacent material instead. Produces `<topic-slug>-sources.md` grouping candidates by primacy (`primary` / `secondary` / `tertiary`). When invoked downstream of `/identify-perspectives`, gr...Votes: 0GitHub stars: 24
- Content DesignUse when someone asks what a surface should communicate or how its copy should feel before final words are written, or when a team needs a cross-surface brand register. Runs in three modes: message and narrative structure for a content brief; per-surface acquisition copy goals for a copy-direction record; brand-level register for named, ranked voice goals and arbitration rules. Use `ux-writing` for final product UI strings and state microcopy, `creative-direction` for visual mood, and `inform...Votes: 0GitHub stars: 24
- Creative DirectionUse when someone says a digital surface should feel premium, calm, playful, or otherwise has a vibe but no shared visual direction. Also use when refining or amending an existing direction, or when inheriting it into a new section, component, or feature. Produces ranked aesthetic goals and, when due, a `<output_dir>/direction/<slug>.md` record grounded in referents and arbitration rules. Use `design-system` after the direction to derive tokens, `information-architecture` for page hierarchy, a...Votes: 0GitHub stars: 24
- Design PrinciplesUse when a design team asks for durable rules that turn journey evidence and opportunity pains into consistent decisions across sprints. Produces 3–5 named design principles, each with rationale and an arbitration test. Use `creative-direction` for visual goals, `design-system` for token taxonomy, and `design-review` to evaluate existing work. Target segments and product positioning belong to product strategy; choosing and scoping a bet belongs to product engineering; encoding rules in compon...Votes: 0GitHub stars: 24
- Design ReviewUse when someone asks to critique an existing rendered screen, flow, or mockup for usability, quality-floor, clarity, and aesthetic-fit problems. Produces a severity-rated findings list grounded in the actual artifact. Use `creative-direction` to name a new visual direction, `information-architecture` to design hierarchy, and `design-system` to derive tokens. Reviewing product strategy or choosing a bet is upstream strategy work; framing the work belongs to `frame-intent`; reviewing code defe...Votes: 0GitHub stars: 24
- Design SystemUse when an approved aesthetic direction or an existing product system exists and someone asks what the design system should actually be — the typography, color, spacing, shape, depth and motion decisions a build can implement. Produces a project-specific system: relationships plus the concrete values that make them executable, derived from the approved direction, the incumbent system and the platform floor. Use `creative-direction` to establish the direction first, `information-architecture`...Votes: 0GitHub stars: 24
- Experience StatusUse when someone asks where the current experience-design thread stands, which design artifacts exist, what is missing, or which design skill comes next. Reads the configured design output and returns a read-only orientation; it never writes files or performs the missing design work. Product or portfolio status belongs to product strategy, prioritizing and shaping the next feature belongs to product engineering, and implementation or build status belongs to frontend engineering. Triggers on \...Votes: 0GitHub stars: 24
- Information ArchitectureUse when someone asks what goes where on a screen or flow, in what order, or how a genre-specific surface helps people understand, navigate, decide, or act. Produces IA and layout specs for general screens and flows plus analytical dashboards/reports/monitoring; conversion landing, home, pricing, and acquisition pages; documentation sites, help centers, API references, and guide sets; informational articles/news/editorial pages; marketplace catalogues/listings/comparison/transaction paths; an...Votes: 0GitHub stars: 24
- Interaction DesignUse when someone asks how one screen or component should respond to actions, validate input, transition, recover, or feel in use. Produces behavioral and state specifications for the interaction. Use `information-architecture` for hierarchy, `user-flow` for cross-screen routes, and `creative-direction` for visual mood; `ux-writing` owns the strings shown in those states. Product strategy is upstream; framing and scoping the feature belongs to `frame-intent`; implementing the state machine, mo...Votes: 0GitHub stars: 24
- Journey MappingUse when a team asks what an end user goes through across an experience, from one meaningful outcome to the next. Produces a customer journey map of stages, actions, touchpoints, emotions, pains, and opportunities, adjusted for the relevant platform. Use `service-blueprint` for backing services, `user-flow` to turn the journey into screens, and `process-mapping` for internal operations. Adoption strategy belongs to product strategy; selecting and scoping a bet belongs to product-engineering s...Votes: 0GitHub stars: 24
- Process MappingUse when a team asks how an internal business operation works today or should work tomorrow across actors and handoffs. Produces a SIPOC scope, swimlane map, as-is/to-be flow, and pain-and-waste register. Use `journey-mapping` for the customer's experience, `service-blueprint` to connect a journey to backstage support, and `user-flow` for screens. Operating or product strategy belongs upstream; shaping an automation bet belongs to `frame-intent`; implementing workflow software belongs to engi...Votes: 0GitHub stars: 24
- Service BlueprintUse when someone asks what people, services, and systems support each step of an existing customer journey. Produces a service blueprint across evidence of service, frontstage, line of visibility, backstage, and support. Use `journey-mapping` to discover the customer path first, `user-flow` for screen transitions, and `process-mapping` for an internal operation without the customer lens. Service strategy belongs upstream; framing the initiative belongs to `frame-intent`; implementing service ...Votes: 0GitHub stars: 24
- User FlowUse when an approved customer journey needs to become screens, transitions, failure paths, and navigation routes. Produces a complete screen sequence plus one self-contained brief per screen and a whole-flow walk-through. Use `journey-mapping` to understand the journey first, `interaction-design` for behavior within one screen, and `service-blueprint` for backing services. Adoption strategy belongs upstream; appetite and scope belong to `frame-intent`; implementing routes and screens belongs ...Votes: 0GitHub stars: 24
- FigmaRead and inspect Figma files (Cloud) via the REST API. Supports fetching files / specific nodes / file metadata / version history / comments, rendering frames to PNG/SVG/JPG/PDF, posting comments (file-level or pinned to a node), converting FigJam connector graphs to Mermaid, and best-effort reads of design tokens (variables) and dev resources where the token's plan allows. Use when the user wants to read, render, comment on, or extract structure from a Figma file. Does NOT modify design cont...Votes: 0GitHub stars: 24
- A11y EngineeringDeep accessibility engineering beyond automated tooling — focus management architecture, ARIA role correctness under dynamic mutation, live-region discipline, keyboard contract specification, and manual checks for WCAG 2.2 Target Size (Minimum) (AA) and Focus Appearance (AAA enhancement), plus a stated gap against the WCAG 2.2 AA baseline. Triggers on "audit this surface for accessibility beyond axe", "fix the focus management in this modal flow", "define the keyboard and screen-reader contra...Votes: 0GitHub stars: 24
- Component ContractDesign a UI component's public interface — props/slots/events, controlled vs. uncontrolled ownership, composition patterns, lifecycle contract, and usage documentation — before writing any implementation. Triggers on "design the public contract for a shared date picker", "define the props, events, and slots before we build this component", "review this shared component's API before we publish it".Votes: 0GitHub stars: 24
- Css ArchitectureOrganize CSS at scale using cascade layers, scoping strategies, and specificity budgets — preventing specificity wars, enabling safe deletion, and making CSS that other engineers can reason about. Triggers on "design the CSS architecture for this new codebase", "fix the specificity wars in our stylesheet", "refactor our cascade so rules can be deleted safely".Votes: 0GitHub stars: 24
- Fe PerformanceMeasure, diagnose, and remediate Core Web Vitals and asset budget violations using structured profiling, causality analysis, and repeatable remediation patterns. Triggers on "diagnose why this route fails LCP", "find the cause of our INP regression", "bring this page back under its asset budget".Votes: 0GitHub stars: 24
- Fe StatusOrient skill — read the current surface's evidence manifest, known exceptions, and gate history to return a surface-state summary against the frontend engineering quality floor. Triggers on "what is the frontend quality status of this surface", "show me the latest gate history and known exceptions", "what should we fix before changing this existing page".Votes: 0GitHub stars: 24
- Frontend EngineeringLoad when a task's primary output is HTML, CSS, or JS. Provides design pre-flight, codified craft rules, GATES verification commands, and an evidence manifest for that surface. Four modes — create (new surface), retrofit (improving existing), audit (review only), verify (run gates and manifest). Triggers on "build this dashboard in HTML, CSS, and JavaScript", "retrofit this existing landing page without breaking its states", "audit this web surface against the frontend quality floor", "verify...Votes: 0GitHub stars: 24
- Rendering StrategySelect and implement the correct rendering model (CSR/SSR/SSG/ISR/RSC) for each route based on data-access patterns, performance targets, and personalization requirements. Triggers on "choose the rendering model for each route in this product", "should this personalized route use SSR or CSR", "audit our docs routes for caching and hydration problems".Votes: 0GitHub stars: 24
- Responsive LayoutDesign and implement adaptive layouts using CSS Grid, Flexbox, container queries, and fluid typography/spacing — the craft layer for layouts that work correctly across all viewport sizes without JavaScript. Triggers on "build this page layout so it works at every viewport", "fix the card grid that breaks at 720 pixels", "make this shared card adapt to its container without JavaScript".Votes: 0GitHub stars: 24
- Token ArchitectureDesign and govern a three-tier CSS custom property token system (primitive → semantic → component), including semantic alias layers, light/dark theming, and DTCG-compatible source generation. Triggers on "design a three-tier token system for our web app", "audit our CSS tokens for hardcoded value drift", "add a semantic dark-theme alias layer", "export our tokens in DTCG format".Votes: 0GitHub stars: 24
- Github Brief IntakeUse when GitHub work should enter the repository work-intake route, including an Issue, Milestone, view, or cross-repository selection.Votes: 0GitHub stars: 24
- Github RefreshReviewed refresh and confirmed GitHub coordination write-back processor for tracker-origin artifacts.Votes: 0GitHub stars: 24
- Generate IacUse this skill to author governed, best-practice Terraform/OpenTofu infrastructure from a plain-language intent. Triggers on "provision X", "create Terraform for", "generate IaC for", "set up cloud resources", "write Terraform for", "scaffold infrastructure". Stops at a digest-pinned `terraform plan` (G4 handoff); never runs `apply`. Governance-first — resolves the decision-record surface before any code.Votes: 0GitHub stars: 24
- Reconcile IacUse this skill to audit Terraform/OpenTofu drift, reconcile state, run a pre-change preflight, or check an incoming IaC diff for ADR compliance. Triggers on "reconcile my infrastructure", "check for drift", "drift audit", "what drifted", "before I change X check drift", "is my infra in sync", "adr-check", "does this change comply", "check this diff against our ADRs", "compliance check this IaC change". Never autonomously applies. Shares generate-iac's references and reviewers.Votes: 0GitHub stars: 24
- Linear Brief IntakeUse when Linear work should enter the repository work-intake route, including an Issue, sub-issues, a Project, Cycle, view, or cross-repository selection.Votes: 0GitHub stars: 24
- Linear Brief SyncUse this compatibility skill when you want to catch up an existing product brief with changes in the linked Linear Issue — "sync the brief with LIN-123", "the Linear issue has been updated, update the brief". It delegates refresh authority, lifecycle checks, and write-back confirmations to the configured `work-intake` Linear refresh processor while preserving the old trigger language.Votes: 0GitHub stars: 24
- LinearRead Linear Issues and Projects via the GraphQL API. Supports fetching individual issues (title, description, identifier, sub-issues, owning project), fetching all issues in a project, verifying credentials, and executing confirmed refresh write-back actions through work-intake. Use when you want to read Linear work items to create briefs or catch up a brief with changes.Votes: 0GitHub stars: 24
- New PackageUse this skill when the user wants to scaffold a new package in the monorepo's `packages/` directory. Triggers on "new package", "create a package called...", "add a library for...". Don't use for new top-level directories (those need an RFC) or for new apps (which go in `apps/`, not `packages/`).Votes: 0GitHub stars: 24
- Align Value StreamUse at business-unit scale to stand up and keep current a value-stream meta-repo — a coordinating repo with no app code that holds the cross-component artifacts a polyrepo has nowhere else to put (the federated Backstage catalog, the shared-contract authority, the C4/bounded-context architecture, and the cross-component delivery rollup). Triggers on "set up a value-stream meta-repo", "coordinate across component repos", "stand up the cross-component catalog", "where does the shared contract l...Votes: 0GitHub stars: 24
- De Risk IntentUse when an intent is framed and you need to test whether the bet holds before building it out — naming the riskiest assumption, predeclaring a kill condition, and running it under a chosen prototype-approach. Triggers on "de-risk this", "is this assumption true", "what would have to be true", "should we validate or just build it", "test the bet". Routes by reversibility (one-way vs two-way door) and ends in a survive/kill verdict. Do NOT use to author the intent (use `frame-intent`) or to br...Votes: 0GitHub stars: 24
- Decompose IntentUse when a de-risked intent needs breaking into the next level down — child intents, or a shippable delivery contract at the leaf — and optionally projecting onto a tracker. Triggers on "decompose this", "break this down", "slice this", "what specs come out of this", "push this to Linear/Jira". Recursive (one level at a time); one independently shippable feature becomes a delivery contract, while multi-spec or cross-repository work becomes a delivery brief. Do NOT use to author an intent (use...Votes: 0GitHub stars: 24
- Discovery LoopUse to turn a raw product idea into a ratified, build-ready decision brief — the upstream discovery loop run by the discovery-lead agent. Triggers on "scaffold the product vision for X", "run a discovery for X", "diverge on the product shape then converge to a brief", "take this idea to a decision brief", "resume the X discovery". It diverges across candidate product shapes, converges the chosen one through a research/product/UX/architecture/safety lens roster, pauses at the consent gates (G0...Votes: 0GitHub stars: 24
- Diverge SolutionsUse at step 3 of the PE shaping sequence when you hold an initiative- or capability-scope opportunity and need structured, comparable solution options that place-bet can reason against. Emits solution-options.md with an options array and a recommendation. Do NOT use for freeform brainstorm (use explore-options), feature-scope divergence (use explore-options), or committing a bet (use place-bet).Votes: 0GitHub stars: 24
- Explore OptionsUse to generate multiple candidate product shapes before the discovery loop converges on one — the divergence stage that guards against myopic-greedy commitment. Triggers on "give me candidate product shapes", "diverge on the product shape", "what are the options before we commit", "explore alternatives for X", "don't converge yet". Generates N candidates across altitude × mechanic, each with its riskiest assumption, then frames an explicit compare-and-choose. Do NOT use to break down a chose...Votes: 0GitHub stars: 24
- Frame DomainUse when grounding a product in the real-world activity it serves and bounding its MVP before any screen, service, or architecture is drawn — at the G1.5 Domain & MVP point of the discovery loop, or standalone. Triggers on "frame the domain", "how is this activity really done", "ground this before we design", "what's in/out of the MVP", "draw the scope boundary", "is this scope creep". Produces two typed artifacts from one research-grounded pass — Domain Framing (real-world-activity grounding...Votes: 0GitHub stars: 24
- Frame IntentUse when shaping a piece of product work before it becomes a spec — turning an idea, a request, or a strategy into a level-tagged `intent` (an outcome + the opportunity behind it). Triggers on "shape this", "what's the intent here", "frame the problem", "before we build X", "turn this into a brief/PRD". Authors an `intent` at any altitude in the open recognized set — product-vision, product-strategy, capability, or feature — resolves Scale (app ↔ business-unit) at intake, and offers current-s...Votes: 0GitHub stars: 24
- Frame SituationUse when holding a raw signal (market observation, OKR gap, user pain pattern, engineering finding, competitive signal) at initiative or capability level — turning it into a typed finding, a Wardley capability maturity assessment, and an anchor into the PE six-step shaping sequence. Triggers on "frame this situation", "what do we do with this signal", "is this an opportunity or a risk", "where should we start", "map this to the shaping sequence". Do NOT use for a feature-scoped request (use `...Votes: 0GitHub stars: 24
- Identify OpportunitiesUse at step 2 of the PE shaping sequence — or directly from a free-form problem description — to surface all JTBD jobs (functional, emotional, social) behind an opportunity area, score each via the Ulwick formula, and produce a ranked `opportunity-assessment.md` artifact. Triggers on "map the jobs", "what do users need", "identify opportunities", "score the opportunity", "step 2 shaping". Do NOT use when a bet is already committed to a solution (use `place-bet`) or when the input is an unclas...Votes: 0GitHub stars: 24
- Lean CanvasUse when a product engineer or PM is ready to produce an initiative brief through an adapted Lean Canvas elicitation — after the PE shaping sequence or as a standalone exercise. Triggers on "lean canvas", "initiative brief", "canvas this initiative", "author initiative brief". Do NOT use for a feature-scoped request (use `frame-intent`) or for individual shaping steps (use `frame-situation`, `place-bet`, etc.).Votes: 0GitHub stars: 24
- Map CapabilitiesStep 6 (terminal) of the PE six-step shaping sequence. Translates a committed bet into a Capability Map — L1 domain organisation, Wardley × strategic-criticality annotation, Build/Buy/Partner/Adopt disposition, and a Build-only suggested build sequence anchoring M3–M6 spec-writing. Run after `place-bet`. Triggers on "map our capabilities", "what do we need to build", "what's our build/buy split", "capability areas for this bet". Do NOT use for a single feature (use `frame-intent`) or to autho...Votes: 0GitHub stars: 24
- Place BetStep 5 of the PE six-step shaping sequence — the bet-commitment gate. Reads a diverge-solutions artifact if present (offers to run it first if absent); accepts options from any source; folds in validation-notes when available; emits bet.md with the full betting table anchoring map-capabilities. Do NOT use to generate options (use diverge-solutions or explore-options) or validate assumptions (use de-risk-intent).Votes: 0GitHub stars: 24
- Plan ValidationUse to turn a converged product's load-bearing assumptions into a validation plan — and to scaffold the primary-research instruments that would test them. Triggers on "plan the validation", "how do we validate these assumptions", "turn assumptions into a validation plan", "scaffold an interview guide / usability test", "what would confirm this". Produces assumption → kill-condition → real-world-activity hooks and the instrument scaffolds (interview guide, usability-test plan, transcript-synth...Votes: 0GitHub stars: 24
- Ux WritingUse when shaping the actual words a user reads in a product's UI — characterizing the UI copy voice (how the brand register applies to UI states), writing recurring UI-state microcopy (error, empty, button, label), or reviewing copy before it ships. Triggers on "what should this error say", "write the empty-state copy", "name this button", "characterize our product's UI copy voice", "make this microcopy blame-free", "review this copy". Characterizes voice along a few axes, writes each UI stat...Votes: 0GitHub stars: 24
- Define Content StrategyUse when a strategist needs to set the organizational content direction before content design begins — the governance and structural layer above per-surface content execution. Triggers on "define the content strategy", "I need to set the content strategy before content design", "content governance framework", "Halvorson content strategy", "Purpose Process Structure Governance". Produces a committed content-strategy.md. Do NOT use to write per-surface content or microcopy — that belongs to the...Votes: 0GitHub stars: 24
- Define Ux StrategyUse when a strategist needs to set the experience direction before design begins — the bridge between business goals and what the designed product must achieve. Triggers on "define the UX strategy", "I need to set the experience strategy before design", "what should our UX strategy be", "align design to business goals", "set the experience vision". Produces a committed ux-strategy.md. Do NOT use to produce a customer journey map — that belongs to journey-mapping in the experience-design pack.Votes: 0GitHub stars: 24
- Run Bcg MatrixUse when a strategist needs to assess portfolio position and derive investment priorities across multiple products or business units. Triggers on "run a BCG matrix", "I need to assess portfolio position", "portfolio growth-share analysis", "which products should we invest in or cut", "star cash cow dog question mark". Produces a committed portfolio-position artifact. Do NOT use for single-product strategy — BCG requires at least two offerings to compare relative market share.Votes: 0GitHub stars: 24
- Run Okr CascadeUse when a strategist needs to cascade company OKRs to team level and identify strategic gaps for the product-engineering shaping queue. Triggers on "run an OKR cascade", "I need to cascade company OKRs", "align team OKRs to company goals", "identify OKR gaps", "what are we missing to hit our objectives". Produces okr-cascade.md and workspace.toml shaping-queue entries. Do NOT use for per-feature goal-setting — cascade is org-wide alignment, not product backlog prioritization.Votes: 0GitHub stars: 24