eq

Plugin eq from marketplace frontend-skills in everquint/frontend-skills. Commands read from the repo's manifest — 1 month ago.

Skills (8)

• eq-design-system

  The design token system — a four-layer boilerplate (brand primitives → semantic tokens → theme overrides → framework mapping) that any project starts from, plus the rebrand, dark-theme and audit procedures. Use when scaffolding a new project's theme file, rebranding an existing one, adding dark mode

• eq-frontend-prototype

  Prototype mode — the reduced gate set for a throwaway repo that answers one question and then gets deleted, plus the expiry and graduation path back to the full standard. Use when starting a prototype, POC, spike or demo that has an expiry date and no users, when deciding which gates such a repo may

• eq-frontend-quality-bar

  The non-lintable half of frontend quality — tests and diff-coverage gates, error reporting, performance budgets, accessibility, client-side security. Use when writing tests, wiring a coverage gate, adding error reporting, setting a bundle budget, verifying accessibility, or reviewing untrusted HTML

• eq-frontend-standards

  One canonical frontend TypeScript standard — lint rules, correctness gates, file budgets, structure, naming, git hooks, commit conventions, CI. Use when setting up or auditing quality tooling, migrating a repo to the standard, or judging whether a lint finding is a real defect.

• eq-frontend-workflow

  Delivery workflow — branch model, branch or worktree, commits, PRs, review, merge, release, rollback, and how to split work between a primary agent and subagents. Use when starting work, briefing a subagent, writing a commit message, opening a PR, running the pre-push gate, deciding whether a change

• eq-code-graph

  Optional, recommended — use a pre-indexed code knowledge graph (codegraph) to answer structural questions about a repo in one tool call instead of grepping and reading. Use when asked "what depends on X", "what's the blast radius of changing X", "how does this feature flow end-to-end", or to trace c

• eq-create-issue

  Write a Linear issue that a PM can read and a dev can execute — one template, two branches — for work about to start, and for work already shipped that has no ticket. Use when asked to create a Linear issue or ticket, file the work just done, turn a conversation or a diff into a ticket, or write acc

• eq-take-issue

  Take a Linear issue, read it against the codebase, settle the approach with the human one question at a time, then build it under the delivery workflow. Use when given a Linear issue ID or URL to implement, asked to pick up a ticket, or asked how a ticket should be built.

Similar plugins