Stats
Actions
Available In
Tags
What's Inside
Skills3
create-issue
/create-issue
Create a well-formed GitHub issue from a vague idea, bug report, or feature request. Use when the user says "create an issue", "open a ticket", "file a bug", "log this in GitHub", "make a backlog item", or describes something that should be tracked. Drafts a structured body and creates the issue via gh CLI.
design-review
/design-review
Professional design review of any UI — a marketing page OR a product internal (dashboard, table, list, detail view, settings, a flow). Actionable, located critique against orientation, information architecture, primary task, visual hierarchy, friction/cognitive load, accessibility, and — for app screens — density, states, navigation, consistency, and data legibility. Use when the user says "review this design", "review this screen", "review this dashboard", "critique this UI", "is this UI good", "review this mock", "design review", "roast my design", "roast my landing page", or drops an HTML file / screenshot for feedback.
measurement-plan
/measurement-plan
Create a measurement plan for a feature using the Goal-Question-Metric (GQM) structure — defines a measurement goal, learning objectives, metrics, and implementation (product analytics events, warehouse tables, event pipeline). Use when user says 'measurement plan', 'GQM', 'goal question metric', 'goal-question-metric', 'measurement goal', 'how do we measure this', 'what metrics for this feature', 'tracking plan', 'analytics requirements', 'how do we know if this works', 'define KPIs for', or when planning a new feature and analytics instrumentation is needed.
README
aictrl Skills
Free, vendor-neutral AI engineering-workflow skills.
Install
Claude Code
/plugin marketplace add aictrl-dev/skills
/plugin install aictrl-skills@aictrl-oss
Cursor / OpenCode — skills use the cross-tool Agent Skills standard:
git clone https://github.com/aictrl-dev/skills && cd skills
./scripts/install.sh cursor # or: opencode | all
…or copy skills/* into your tool's skills dir (~/.cursor/skills, ~/.config/opencode/skills).
Then invoke any skill: /design-review, /measurement-plan, /create-issue.
The Skills
| Skill | What it does | Try it |
|---|---|---|
| design-review | Drop an HTML mock or screenshot — get a sharp, located critique across IA, value prop, hierarchy, trust/friction, and a11y. Ends with "Fix these 3 first." | /design-review path/to/mock.html |
| measurement-plan | Feature → structured measurement plan: learning objectives, metrics table, product-analytics events, warehouse changes, event pipeline. | /measurement-plan |
| create-issue | Vague idea or bug → well-formed GitHub issue with context, acceptance criteria, and no vague hand-waving. Creates it via gh after you confirm. | /create-issue |
design-review in action
Input: a SaaS landing page mock.
Value Proposition — WEAK
Hero headline "Workflows made simple" says nothing about what the product does.
Fix: replace with a one-liner that names the user, the problem, and the outcome.
Actionability — BROKEN
Three competing CTAs above the fold (Start free, Book demo, Watch video).
Fix: one primary CTA above the fold; demote the others below.
Every critique names the element. Every fix is concrete. No generic "improve clarity."
Why these exist
These are the engineering workflows aictrl automates at scale. The skills teach the method — aictrl operationalizes it, grounded in your backlog, team standards, and codebase knowledge graph. The skills are free and standalone; aictrl is the layer that makes them continuous and codebase-aware.
Contributing
PRs that add skills are welcome — see CONTRIBUTING.md.
Stats
Version0.4.0
LanguageHTML
Stars0
MaintenanceGood
LicenseMIT
Last Commit
Added
Available In
