Borrowing it
Nothing to install: this file belongs to luiscielak/ai-product-design-rules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luiscielak/ai-product-design-rules/main/.cursor/skills/ai-product-design-ui-proto/SKILL.mdgit clone --depth 1 https://github.com/luiscielak/ai-product-design-rulesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/luiscielak/ai-product-design-rules/ai-product-design-ui-proto)<a href="https://agentmods.dev/skills/luiscielak/ai-product-design-rules/ai-product-design-ui-proto"><img src="https://agentmods.dev/badge/skills/luiscielak/ai-product-design-rules/ai-product-design-ui-proto/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/luiscielak/ai-product-design-rules/ai-product-design-ui-proto"><img src="https://agentmods.dev/badge/skills/luiscielak/ai-product-design-rules/ai-product-design-ui-proto.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00057 | $0.00816 |
| Opus 5.5 | $0.00023 | $0.00326 |
| Sonnet 5.5 | $0.00011 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
ai-product-design-ui-proto scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Prototype (UI Engineer)
Implement a runnable prototype (shadcn/ui + Tailwind), keyboard/focus-accessible, covering primary flows.
Pipeline
Final stage in the ai-product-design chain:
scaffold → /prd → /lofi → /midfi → /hifi → /ui-proto.
- Previous:
/hifi(ai-product-design-hifi) — implement theui-design/kit - Next: — (end)
To run the whole chain in one pass, use the ai-product-design-workflow
orchestrator. When an existing design system is named (e.g. Konstrukt), prefer
its CSS/tokens over a fresh shadcn install and record the deviation in
README-proto.md.
Inputs
| Input | Notes |
|---|---|
framework |
default: Next.js 14+ App Router |
package_manager |
npm |
ts |
default: true |
pages |
List of pages/screens |
components |
From mid-fi |
routes/flows |
Primary navigation and flows |
data |
mock or live |
theming |
light |
Artifact root
All deliverables for this product go under a single artifact_root:
- Definition:
artifact_rootis the directory that contains this product’sPRD.mdand/orDESIGN-BRIEF.md(same folder is ideal). If files are split, prefer the folder the user attached or the one containingPRD.md. - Resolve in order: (a) Parent directory of an attached or @-referenced
PRD.md/DESIGN-BRIEF.md; (b) explicit path the user gives for the product docs folder; (c) greenfield only (/new-projector PRD with no path):projects/{project_name}/docs/. - Do not default to repo-global
docs/wireframes/,docs/ui-design/, or rootdocs/PRD.mdwhenartifact_rootis known.
Inputs path: Read mid-fi wireframes and specs from {artifact_root}/wireframes/midfi/ (not repo-global docs/wireframes/midfi/).
Output
- Next.js app under
{artifact_root}/prototype/(create that directory if missing): Tailwind configured, shadcn installed - Routes/pages per screens; mock data and API stubs as needed
{artifact_root}/prototype/README-proto.md— setup, components, routes, known gaps
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 72 lines · 57 tokens per session scan A f831f8f53a1d
ai-product-design-ui-proto is a skill published in the GitHub repository luiscielak/ai-product-design-rules (4 stars, last pushed 5d ago), licensed MIT. It adds 57 tokens to every session and 816 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-28.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
ui-checkstyle
Run the exact ESLint + Prettier + organize-imports sequence that CI's UI Checkstyle workflow runs — on just the files the PR changed — and fail the task if any file ends up with a diff. Invoke after authoring or modifying any .ts, .tsx, .js, .jsx, or .json file under openmetadata-ui/src/main/resources/ui/src/…
tamagui-v6-config
Tamagui v6 theme system: the light/dark/accent/brand/inverse/level/active theme family, the background-active one-off key, and recipe-tree authoring with createV6Config. Use when choosing a theme for a surface, building a selected/emphasis state, or authoring a custom v6 colors pack.
tamagui-theme-generator
Generate custom Tamagui themes, color palettes, and preview URLs. Use when creating or refining a color scheme, authoring light/dark palettes with brand accents, or previewing generated themes in the browser.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
building-landing-home
Compose a product or documentation home page from the @lobehub/ui/awesome landing components: LandingHero, AgentSkillCard, LogoMarquee, LandingSection, BentoGrid/BentoCard, CodeShowcase, FeatureGrid, InstallBanner and FluidGradient. Covers page structure, the lobedocs homePage hook, router links, theming the accent…