eugenelim
- 147 skills
- 0 followers
- 21 hours ago last updated
- ▌ 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".
- ▌ Argv Flag · eugenelim bundleCredentialed-CLI fixture whose script accepts `--token` on argv; an argv-flag finding is expected.
- ▌ 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.
- ▌ Conforming · eugenelim bundleA credentialed-CLI fixture skill that satisfies every lint check; lint should report zero findings.
- ▌ 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).
- ▌ Dotfile Grep · eugenelim bundleCredentialed fixture whose script opens `.agentbundle/credentials.env` directly without the opt-out marker; a dotfile-read finding is expected.
- ▌ 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.
- ▌ Argv Flag Derived · eugenelim bundleCredentialed-CLI fixture exercising round-2 lint widening — f-string, Starred(Tuple), Subscript shapes. All three should produce argv-flag findings.
- ▌ 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.
- ▌ MCP Server Headers · eugenelim bundleMCP-server class fixture using header-naming flags (`--bearer-header`); the argv-flag ban is scoped to credentialed-cli only — lint must NOT flag this fixture.
- ▌ Missing Dont Block · eugenelimCredentialed-CLI fixture missing the `### Security rules (non-negotiable)` heading; a missing-block finding is expected.
- ▌ Dotfile With Optout · eugenelim bundleCredentialed primitive that legitimately reads the dotfile, with the opt-out marker on the same line; lint must NOT flag it.
- ▌ 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.
- ▌
- ▌