eugenelim
- 173 skills
- 0 followers
- 28 repo stars
- 6 days ago last updated
- ▌ Confluence Crawler · eugenelim bundleCrawl an authenticated Confluence space (Atlassian Cloud or on-prem Server/Data Center) by page hierarchy and convert each page to clean Markdown with frontmatter. Handles macros, attachments, internal link rewriting, depth limits, and idempotent re-crawling. Use when the user wants to mirror, export, or ingest Confluence content.
- ▌ Jira Align Refresh · eugenelim bundleReviewed Jira Align refresh processor with fail-closed unsupported write-back capability.
- ▌ Write Prfaq · eugenelim bundleUse when a strategist needs to write the press release before the product exists — an altitude-0 forcing function that surfaces what the product must be before any engineering begins. Triggers on "write a PRFAQ", "I need to write the press release before the product", "altitude-0 forcing function", "press release FAQ format", "Amazon PRFAQ". Produces a committed prfaq.md. Do NOT use as a product spec or backlog — PRFAQ is a direction artifact, not an implementation contract.
- ▌ Devils Advocate · eugenelim bundleAdversarially review a research artifact (`<topic-slug>-survey.md`) or a user-supplied claim. Searches for counter-evidence, names the strongest objections, and routes each to a verdict — either a confidence-rating downgrade or a do-not-resolve verdict for an irreducible tension where both sides are well-evidenced under different conditions. Grounded in ACH (evidence-against column — the discipline that catches premature closure) and GIJN investigative-journalism practice ("what does the other side say"). Auto-invoked by `/desk-research` deep mode against `<topic-slug>-survey.md`; runs standalone against any user-supplied claim. Produces `<topic-slug>-counterpoints.md` linking back to the source artifact. Depth cues — `quickly`, `top three`, `briefly`, `summary only` for the strongest objections; `comprehensively`, `exhaustively`, `in depth`, `extensive` for the full set.
- ▌ Place Bet · eugenelim bundleStep 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).
- ▌ New Guide · eugenelim bundleCreate or substantially revise user guides, pack pages, and journey pages using Diátaxis plus conversation-first UX. Use when asked to write, simplify, restructure, audit, or modernize tutorials, how-to guides, reference pages, explanations, pack pages, or journey pages so readers can start from a natural-language goal, see what to say, understand what happens next, and reach an outcome without learning internal skill names first. Do NOT use for feature contracts (use `new-spec`), cross-cutting proposals (use `new-rfc`), recording decisions (use `new-adr`), minor single-line edits (normal PR), contributor docs, docstrings, release notes, or blog posts.
- ▌ Confluence Publisher · eugenelim bundlePublish content to a Confluence page (Atlassian Cloud or Server/Data Center) by creating a new page or updating an existing one. Accepts Markdown (default), raw Confluence storage XHTML, or plain text. Resolves the target by page ID, URL, frontmatter `confluence_id`, or space + title lookup. Handles optimistic-locking 409s with one retry. Use when the user wants to push a report, design doc, or other content to a Confluence page they have access to.
- ▌ Fe Status · eugenelim bundleOrient 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".
- ▌ UX Writing · eugenelim bundleUse 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 state from a blame-free + actionable formula, and runs a content checklist. When a per-screen state matrix from `user-flow` is present, writes copy per screen × state keyed to the matrix; when absent, behaves as today. Do NOT use to frame the intent behind the feature (use `frame-intent`), to make visual or layout design decisions, to write documentation prose (use `new-guide`), or to establish the brand-level copy register (use `tone-of-voice`).
- ▌ Define Slo · eugenelimUse to author a Service Level Objective (SLO) document for a service in the release-engineering pack. Produces an OpenSLO v1 YAML file committed to `slos/<service>.yaml`, with an error_budget_policy block, that the release-loop's PRR gate reads to resolve the error-budget status field. Triggers on "define SLOs for this service", "author an SLO", "set up error budget tracking", "create a reliability target", "we need an SLO document", "the PRR shows error-budget: not-defined". Do NOT use to generate Prometheus recording rules or alerting rules (toolchain work — the adopter's pipeline does that), to set up ongoing alerting backend routing, or to run the release loop itself.
- ▌ Design Review · eugenelim bundleUse 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 defects or implementation quality belongs to frontend engineering. Triggers on "review this checkout flow for usability problems", "critique this landing page mockup against our design principles", "what's wrong with this rendered dashboard".
- ▌ Design System · eugenelim bundleUse when an approved aesthetic direction exists and someone asks how to name and organize semantic tokens, spacing, type, or color scales. Produces a token taxonomy and rationale; it does not implement token values. Use `creative-direction` to establish the vibe, `information-architecture` for page hierarchy, and `design-review` to evaluate an existing surface. Product differentiation belongs to product strategy; framing a design-system initiative belongs to `frame-intent`; implementing tokens or components belongs to `frontend-engineering`. Triggers on "derive a semantic token taxonomy from this aesthetic direction", "organize our spacing, type, and color scales by role", "design the token system without choosing implementation values".
- ▌ Tone Of Voice · eugenelim bundleUse when a team asks how the brand should sound consistently across channels and surfaces. Produces a brand-register document with named, ranked voice goals and arbitration rules. It is the upstream anchor: `content-design` owns a surface's message and structure, `copy-direction` owns acquisition-surface copy goals, and `ux-writing` owns product UI strings. Organization-level product or content strategy belongs to the strategy packs; shaping a product initiative belongs to `frame-intent`; implementing copy in templates or components belongs to `frontend-engineering`. Triggers on "define how our brand should sound across product and marketing", "name and rank our cross-surface voice goals", "create a brand register for our support, sales, and product copy".
- ▌ Lean Canvas · eugenelim bundleUse 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.).
- ▌ Run Bcg Matrix · eugenelim bundleUse 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.
- ▌ Compare Hypotheses · eugenelim bundleCompare competing hypotheses on a decision-shaped question using an ACH-style evidence matrix (hypotheses × evidence-for/against). Dispatches per-hypothesis parallel retrieval on Claude Code (one `evidence-retriever` subagent per hypothesis — the +81% parallelizable-task case from multi-agent research). In decision-pipeline invocations expects upstream `<topic-slug>-perspectives.md` and `<topic-slug>-sources.md`; standalone invocations enumerate hypotheses inline. Produces `<topic-slug>-hypotheses.md` with the matrix and a most-supported ranking. Depth cues — `quickly`, `top three`, `briefly`, `summary only` for the dominant hypotheses; `comprehensively`, `exhaustively`, `in depth`, `extensive` for fringe ones too.
- ▌ Content Design · eugenelim bundleUse when someone asks what a surface should communicate, to whom, in what form, and in what order before wireframes or final copy. Produces a content brief for acquisition, product, or reference surfaces. It owns message and narrative structure; `tone-of-voice` owns the brand register, `copy-direction` owns acquisition-surface copy goals, and `ux-writing` owns product UI strings. Organization-level content strategy belongs to `define-content-strategy`; feature framing belongs to `frame-intent`; page or content-system implementation belongs to `frontend-engineering`. Triggers on "create a content brief for our onboarding flow", "decide what this pricing page needs to say and in what order", "shape the message hierarchy before we wireframe the help page".
- ▌ Copy Direction · eugenelim bundleUse when someone asks what the copy on one marketing or acquisition surface should feel like before the lines are written. Produces ranked, grounded copy goals and a `copy-direction.md` record for that surface. `tone-of-voice` owns the cross-surface brand register, `content-design` runs first to decide message and narrative structure, and `ux-writing` owns product UI strings. Product or growth strategy belongs to product strategy; framing the acquisition bet belongs to `frame-intent`; implementing the surface belongs to `frontend-engineering`. Triggers on "name the copy direction for our pricing page before we write it", "what should this onboarding campaign sound like", "set ranked copy goals for this landing page".
- ▌ Frame Domain · eugenelim bundleUse 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 + best practice + naive-failure modes, plus a brownfield current-system half) and Scope Boundary (the MVP out-of-scope register). Do NOT use to shape the intent behind the work (use `frame-intent`), to test whether a bet holds (use `de-risk-intent`), or to break an intent down (use `decompose-intent`).
- ▌ Frame Intent · eugenelim bundleUse 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-state inputs only when brownfield. Do NOT use to test an assumption (use `de-risk-intent`) or to break an intent down (use `decompose-intent`).
- ▌ Run Okr Cascade · eugenelim bundleUse 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.
- ▌ Release Loop · eugenelim bundleUse to drive the deployed end-to-end validation outer loop — deploy the integrated whole to an ephemeral environment, run e2e, observe telemetry, feed deployed findings back to work-loop's inner loop, redeploy, and iterate until the deployed whole converges, then stop at the human consent gate for the prod ship. Run by the release-lead agent (a peer of work-loop's supervisor, not a work-loop mode). Triggers on "run the release loop", "deploy the integrated whole and iterate", "ship it to an ephemeral env and run e2e", "iterate the deployed env until it converges", "take this to a prod-ship readiness record". Autonomy is carved by minimum-regret — reversible ⇒ autonomous on ephemeral envs; irreversible ⇒ human. No engine. Do NOT use for the inner local build loop (use work-loop), to author a fidelity-ladder / local-infra-equivalents skill (that is the inner-loop obligation), or to run the live product as a managed service (adopter ops).
- ▌ Jira Align Brief Intake · eugenelim bundleUse when Jira Align work should enter the repository work-intake route, including one item, a Feature, a program selection, or a cross-repository outcome.
- ▌ Journey Mapping · eugenelim bundleUse 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 shaping; implementing journey screens belongs to `frontend-engineering`. Triggers on "map the customer journey from trial signup to first value", "show what a new admin goes through when setting up a workspace", "map the pains and opportunities in our returns experience".
- ▌ Process Mapping · eugenelim bundleUse 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 engineering. Triggers on "map our monthly close process as it works today", "show the handoffs in our supplier invoice process", "design the to-be process for customer refunds".
- ▌ Decision Archaeology · eugenelim bundleReconstruct the rationale for a past decision by walking time-ordered artifacts (commits, PRs, design docs, chat logs, internal memos). Self-contained — does not invoke `/source-map` or other research-pack skills, because the source surface is time-ordered and internal, and authority is established by an artifact's place in the history rather than by external curation. Produces `<topic-slug>-archaeology.md` with chronology, the rationale chain, the alternatives that were considered and rejected, and a revival check flagging rejected alternatives whose original rejection rationale no longer holds. Depth cues — `quickly`, `top three`, `briefly`, `summary only` for the main rationale chain; `comprehensively`, `exhaustively`, `in depth`, `extensive` for branch alternatives and dead ends.
- ▌ Workspace Design · eugenelim bundleUse when someone asks how a productivity, collaboration, or agentic workspace should support sustained professional work across sessions. Produces a workspace-surface specification covering context persistence, collaboration state, ambient attention, interruptions, and session arcs. Use `analytical-design` for dashboards and monitoring views and `marketplace-design` for exchange surfaces. Product strategy is upstream; choosing the appetite and scope belongs to product engineering; implementing the workspace or writing its UI strings belongs to frontend engineering and `ux-writing`. Triggers on "design the session flow for our collaborative editor", "how should this agent workspace preserve context between sessions", "structure interruptions and handoffs in our team workspace".
- ▌ De Risk Intent · eugenelim bundleUse 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 break it down (use `decompose-intent`).
- ▌ Discovery Loop · eugenelim bundleUse 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 vision, G1.5 altitude/MVP, G2 the "what"), emits a connected hypothesis with validation hooks, and hands off to work-loop at G3 — with no new engine, scheduler, or service. Do NOT use to build a spec (use new-spec → work-loop), to ship one (the release loop), or to author one discovery artifact standalone (use frame-intent / frame-domain / explore-options directly).
- ▌ Credential Setup · eugenelim bundleInteractive credential setup for skills declaring `metadata.auth` of creds. Walks the user through entering each required key from the skill's `creds-schema.toml` and writes to the highest-available tier (OS keychain on Darwin/Windows; 0600 dotfile floor on Linux). Triggers on "set up credentials", "credential setup", "credential broker setup". This is interactive, user-invoked, do not auto-run.
- ▌ Identify Perspectives · eugenelim bundleEnumerate the named camps on a contested topic before research begins. Builds the perspective scaffold that `/source-map` and `/compare-hypotheses` consume downstream in the decision pipeline. Grounded in Wikipedia NPOV (neutral point of view — fairly represent significant views) and ACH (competing hypotheses — surface all explanations before evaluating). Produces `<topic-slug>-perspectives.md` listing each camp's name, its core claim, and representative voices, plus a tension map recording which disagreements are irreducible (both sides right under different conditions) and what a forced resolution would destroy. Depth cues — `quickly`, `top three`, `briefly` for the dominant few; `comprehensively`, `exhaustively`, `in depth`, `extensive` for fringe and dissenting positions too.
- ▌ Analytical Design · eugenelim bundleUse when someone asks how a dashboard, report, or monitoring view should help a user understand data and act. Produces domain-model-first information architecture and a widget hierarchy for the analytical surface, not individual chart implementations. Use `interaction-design` for component behavior, `conversion-design` for marketing surfaces, and `workspace-design` for sustained-work tools. Metric and outcome strategy belongs upstream; shaping the analytics product belongs to `frame-intent`; implementing charts and data bindings belongs to frontend engineering. Triggers on "design a dashboard that helps on-call engineers spot and act on service degradation", "structure this sales report around the questions leaders need answered", "define the widget hierarchy for our monitoring view".
- ▌ Conversion Design · eugenelim bundleUse when someone asks how to structure a landing page, product homepage, pricing page, or acquisition flow so a qualified visitor understands the offer and can act. Produces information architecture and structural specifications for a conversion surface. Use `content-design` for its message hierarchy and `copy-direction` for its copy goals; use `user-flow` and `interaction-design` for product UI. Go-to-market strategy belongs upstream; shaping the acquisition initiative belongs to `frame-intent`; writing final copy or building the page is not this skill's job. Triggers on "structure our pricing page to turn qualified visitors into trials", "design the conversion flow for our product homepage", "spec the hero and scroll story for this landing page".
- ▌ Design Principles · eugenelim bundleUse 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 components belongs to frontend engineering. Triggers on "turn these journey pains into design principles", "give us rules to settle recurring design debates", "what principles should guide this product".
- ▌ Experience Status · eugenelim bundleUse 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 "where are we with the design", "what experience artifacts do we have", "what's next in the design".
- ▌ Service Blueprint · eugenelim bundleUse when someone asks what people, services, and systems support each step of an existing customer journey. Produces a service blueprint across 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 calls or frontend behavior belongs to engineering. Triggers on "blueprint the services behind our account-opening journey", "map what happens backstage at each checkout step", "connect this customer journey to the teams and systems that support it".
- ▌ Fe Performance · eugenelim bundleMeasure, 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".
- ▌ Explore Options · eugenelim bundleUse 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 chosen approach (use `decompose-intent`), to critique one produced artifact (use `devils-advocate`), or to converge (that is the discovery loop's job).
- ▌ Frame Situation · eugenelim bundleUse 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 `frame-intent`), testing an assumption (use `de-risk-intent`), or breaking down a shaped intent (use `decompose-intent`).
- ▌ Plan Validation · eugenelim bundleUse 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-synthesis frame). Do NOT use to run the sessions (out of charter — a human runs them), to test a single bet (use `de-risk-intent`), or to converge (the discovery loop's job).
- ▌ Define UX Strategy · eugenelim bundleUse 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.
- ▌ Creative Direction · eugenelim bundleUse when someone says a digital surface should feel premium, calm, playful, or otherwise has a vibe but no shared visual direction. Produces ranked aesthetic goals and a `creative-direction.md` record grounded in referents and arbitration rules. Use `design-system` after the direction to derive tokens, `information-architecture` for page hierarchy, and `design-review` to critique existing work. Product positioning belongs to product strategy; framing or scoping the bet belongs to `frame-intent`; implementing colors, type, or components belongs to `frontend-engineering`. Triggers on "turn this calm, premium vibe into a shared visual direction", "name and rank the aesthetic goals for our mobile app", "ground this visual mood before we choose colors and type".
- ▌ Interaction Design · eugenelim bundleUse 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, motion, or component code belongs to `frontend-engineering`. Triggers on "design how this search component validates, loads, and recovers", "map the state transitions inside this checkout form", "spec the feedback and motion for this async button".
- ▌ Marketplace Design · eugenelim bundleUse when someone asks how a catalogue, listing grid, comparison view, detail page, or transaction bridge should help participants discover and choose in a marketplace. Produces information-architecture specifications for search, filters, listings, comparison, and the path to transaction. Use `conversion-design` for a single-product marketing page and `workspace-design` for an internal management tool. Marketplace strategy is upstream; framing and sizing the marketplace bet belongs to product engineering; implementing search, filters, transactions, or listing copy belongs elsewhere. Triggers on "design the filters and listing hierarchy for our contractor marketplace", "structure this catalogue for browse-first buyers", "spec the comparison and transaction path for our service listings".
- ▌ Decompose Intent · eugenelim bundleUse 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 `frame-intent`) or to test a bet (use `de-risk-intent`).
- ▌ Map Capabilities · eugenelim bundleStep 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 author a brief (use `lean-canvas` / `author-delivery-brief create`).
- ▌ Run Pestle Analysis · eugenelim bundleUse when a strategist needs to scan the macro environment before setting strategy or evaluating market entry. Triggers on "run a PESTLE", "I need to understand the macro environment", "political economic social analysis", "macro scan", "what external forces affect us". Produces a committed macro-environment artifact. Do NOT use as a substitute for current intelligence — PESTLE organizes and prioritizes information you supply; it does not generate market research.
- ▌ A11Y Engineering · eugenelim bundleDeep accessibility engineering beyond automated tooling — focus management architecture, ARIA role correctness under dynamic mutation, live-region discipline, keyboard contract specification, and manual WCAG 2.2 AA verification for the two criteria automated tools miss. Triggers on "audit this surface for accessibility beyond axe", "fix the focus management in this modal flow", "define the keyboard and screen-reader contract for this data grid", "verify WCAG 2.2 AA manually".
- ▌ CSS Architecture · eugenelim bundleOrganize 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".
- ▌ Diverge Solutions · eugenelim bundleUse at step 3 of the PE shaping sequence when you hold an initiative- or capability-scope opportunity and need ≥3 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).
- ▌ Documentation Design · eugenelim bundleUse when someone asks how a documentation site, help center, API reference, or guide set should be organized so readers reach first value. Produces content-type, information-architecture, and navigation specifications that scale with the corpus. Use `conversion-design` for marketing surfaces and `informational-design` for editorial reading surfaces. Organization-level documentation strategy is upstream; shaping a docs-platform initiative belongs to product engineering; authoring the technical content or building the site and theme belongs elsewhere. Triggers on "design the navigation and content types for our API docs", "structure this help center so readers reach first value", "choose the right information architecture for our 250-page guide set".
- ▌ Informational Design · eugenelim bundleUse when someone asks how an article, news page, editorial feature, or other long-form informational surface should support sustained reading. Produces typography, hierarchy, and reading-flow specifications for the surface. Use `documentation-design` for task/reference systems, `conversion-design` for acquisition pages, and `workspace-design` for tools. Editorial or product strategy is upstream; shaping a publishing-product bet belongs to product engineering; writing the article or building its template belongs to content authors and frontend engineering. Triggers on "design the reading experience for this long-form article", "structure this editorial page for sustained reading", "spec the typography and reading flow for our news feature".
- ▌ Responsive Layout · eugenelim bundleDesign 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".
- ▌ Align Value Stream · eugenelim bundleUse 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 live", "is this feature delivered across all the repos". Reads the per-component slices that decompose-intent produces and rolls up their delivery. Do NOT use at app scale (use decompose-intent — the leaf is one repo's brief) or to author an intent (use frame-intent).
- ▌ Architecture Lenses Reference · eugenelim bundleRoute into the compiled OKF bundle `architecture-lenses` using generated indexes.
- ▌ Component Contract · eugenelim bundleDesign 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".
- ▌ Rendering Strategy · eugenelim bundleSelect 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".
- ▌ Token Architecture · eugenelim bundleDesign 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".
- ▌ Define Content Strategy · eugenelim bundleUse 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 content-design skill in the experience-design pack.
- ▌ Run Porters Five Forces · eugenelim bundleUse when a strategist needs to understand the competitive dynamics of an industry before setting market positioning. Triggers on "run Porter's Five Forces", "I need to understand the competitive landscape", "map industry attractiveness", "how competitive is this market", "supplier and buyer power analysis". Produces a committed competitive-landscape artifact. Do NOT use for individual competitor profiling — this is an industry-structure analysis, not a competitor teardown.
- ▌ Ase Okf Reference · eugenelim bundleNot a selectable skill. Inert reference data invoked only by another skill's explicit agent-skill-engineering-reference/v1 provider call. It answers no user request, performs no user task, and must never be chosen to satisfy a user's question on any subject. When a user's request matches this data's subject, the correct choice is the workflow skill that serves that request, never this one. Its capability declaration lives in metadata.knowledge-provider.
- ▌ Desk Research Project Check · eugenelimPassive stop-signal for a research project — reads the synthesis matrix and memos by eye and reports whether the corpus has stopped changing the structure (theoretical saturation), plus a recommendation. Triggers on project-lifecycle phrasing — "is this project saturated", "should I keep gathering", "check the stop signal" — inside an existing project folder. It NEVER advances phase and computes no counter, score, or metric; the saturation judgment is qualitative and the human decides. It MAY optionally write a verdict_status string into overview.md (the single permitted light state write) — nothing more. Prompt-only by construction.
- ▌ Desk Research Project Start · eugenelim bundleStart a stateful, multi-week research project — the lifecycle axis, orthogonal to the depth axis the `/research` skill carries. Triggers on explicit project-lifecycle phrasing — "start a research project", "set up a research project on X", "begin a sustained investigation", "open a research dossier" — never on a one-shot lookup. Scaffolds the three-layer project folder (overview.md + a raw sources/ layer + the later digest and synthesis), records the question and a possibly-empty working hypothesis, and sets phase to capture. Resolves output_dir: user-scope ~/.agentbundle/agentbundle-layout.toml [research] output_dir first (personal vault always wins regardless of which repo is active), then repo-scope, then two-branch elicitation (repo vs personal workspace) — never a silent .context/ default. Prompt-only: phase is a frontmatter string the agent reads and writes; no engine, index, daemon, or counter. Does not replace /research — episodic quick/standard/applied/deep lookups stay there.
- ▌ Frontend Engineering · eugenelim bundleLoad 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 this completed component and produce its evidence manifest".
- ▌ Desk Research Project Digest · eugenelimBuild the digest middle layer of a research project — the constructed-column synthesis matrix and analytic memos the pack previously lacked. Triggers on project-lifecycle phrasing — "digest the sources", "build the synthesis matrix", "cluster what I've gathered" — inside an existing project folder. Reads sources/*.md, clusters each source's contribution into emergent columns (rows = sources, columns constructed from the material, never a fixed pillar set) in synthesis-matrix.md, and writes analytic memos.md where the working hypothesis is formed and revised. Prompt-only: no engine, no scoring, no fixed schema. Advances no phase on its own — the human moves capture → digest → synthesize.
- ▌ Desk Research Project Status · eugenelim bundleOrient to the current desk-research project at a glance — reads overview.md and surfaces phase, working hypothesis, stop-signal verdict, and what to do next. Triggers on 'where are we on the X research', 'status of the Y investigation', 'resume the Z project', 'what phase is the research in', 'where did we leave off on the research', or any return-to-a-named-research-project phrasing. Read-only: never advances phase, never modifies any file.
- ▌ Information Architecture · eugenelim bundleUse when someone asks what goes where on a screen or flow, in what order, and how users stay oriented. Produces an information-architecture and layout-reasoning document covering hierarchy, reading flow, progressive disclosure, navigation, and wayfinding. Use `creative-direction` for visual mood, `interaction-design` for within-screen behavior, `user-flow` for screen sequence, and `design-review` for critique. Product direction belongs to product strategy; scoping the feature belongs to `frame-intent`; writing markup and styles belongs to `frontend-engineering`. Triggers on "decide what goes where on this settings screen", "design the hierarchy and wayfinding for this flow", "organize this account settings content around the user's primary task".
- ▌ Identify Opportunities · eugenelim bundleUse 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 unclassified raw signal (use `frame-situation` first).
- ▌ Cost Engineering · eugenelim bundleRoute into the compiled OKF bundle `cost-engineering` using generated indexes.
- ▌ Desk Research Project Synthesize · eugenelim bundleSynthesize a research project into its typed verdict and a self-contained governance brief. Triggers on project-lifecycle phrasing — "synthesize the project", "write up the findings", "produce the brief" — inside an existing project folder. Reads synthesis-matrix.md + memos.md and writes BOTH the project's own typed synthesis (<type>.md, named by the project's shape) AND a single-file <topic-slug>-brief.md that governance can lift whole into an RFC. Applies GRADE confidence + ≥3-source triangulation; warns when the matrix is empty (digest was skipped). The brief is answer-first, self-contained, cited and per-finding confidence-tagged, with a Known unknowns section. Prompt-only: advances no phase on its own.
- ▌ Synthesize Stakeholder Research · eugenelim bundleUse when a strategist needs to turn existing stakeholder research into a strategic narrative organized by theme. Triggers on "synthesize stakeholder research", "I need to turn research into strategic direction", "what does the research tell us strategically", "consolidate stakeholder perspectives", "research synthesis for strategy". Requires existing research inputs — surfaces a diagnostic when none are found. Do NOT use to conduct research — this skill synthesizes; it does not interview, survey, or produce primary research.
- ▌ Author Or Update Agent Skill · eugenelim bundleUse when the user asks to frame or design an agent skill, design its trigger or activation boundary, create or author a portable skill or SKILL.md, or change, edit, or update an existing agent skill or SKILL.md. Any request whose outcome is a changed skill file belongs here, including one that also constrains what must stay the same. Select it first and resolve the target inside the workflow, including when the request points at "this skill" with nothing attached, names no file, or is otherwise unresolved - identifying the target and mode is this workflow's first step, and it stays read-only until you authorize a write. Do not use for review-only requests or unrelated writing, coding, architecture, or repository maintenance.
- ▌ Review Or Optimize Agent Skill · eugenelim bundleUse when the user asks to review, audit, tune, or optimize an agent skill or SKILL.md for trigger precision, progressive disclosure, portability, deterministic mechanics, authority, or security. Select it first and resolve the target inside the workflow, including when the request points at "this skill" with nothing attached or names no file; it stays read-only until you authorize a change. Optimization requires an observed failure or measured baseline. Do not use to frame, create, or update a skill - a request to change one while keeping its activation boundary or any other property intact is still an update and belongs to the authoring workflow instead - nor for generic code review, prose editing, repository cleanup, unmeasured rewriting, or unrelated architecture.