wild-frontend
Wild Frontend
Create highly original, production-grade frontend artifacts where memorability, concept, and visual ambition matter more than product consistency.
Use this skill only when explicitly invoked. Build real working code, not just a description.
For multi-step work, start with a short user-visible update that names the concept or first implementation surface you are checking.
Goal
Choose one strong visual concept and execute it with discipline. The result should be distinctive, cohesive, functional, responsive, and usable.
Success Criteria
- The result is real working code in the requested stack.
- One concept drives typography, color, layout, surface, texture, and motion.
- The interface is surprising and memorable without blocking usability.
- Important text is readable, core controls are accessible enough for the task, and decorative effects do not interfere.
- Relevant interaction states and common viewport sizes are handled.
More from marcellocurto/skills
github-issue-create
Draft and create GitHub issues with `gh`. Use for bugs, tasks, features, PRDs, specs, epics, sub-issues, blockers, and tracer-bullet vertical issue breakdowns. Draft first. After approval, create issues and approved native GitHub relationships in the same turn.
11bug-fix-planner
Plan a concrete fix for a specific bug, regression, crash, failing test, error, or broken behavior without changing code. Use when the user wants a path forward from a bug report, GitHub issue, stack trace, logs, screenshots, repro steps, or failing test. Do not use for new features, broad refactors, general debugging advice, or requests to directly implement the fix.
7design-system-ui
Design and implement polished frontend UI that feels native to the existing product, codebase, component library, and design system. Use for normal production frontend work where the result should extend real project patterns rather than invent a disconnected visual direction.
7relentless-review
Relentlessly stress-test proposals, plans, implementations, designs, strategies, or answers. Use when the user asks "is this actually the best we can do?", wants assumptions challenged, edge cases explored, failure modes examined, or asks to push harder, red-team, find holes, or be relentless. The answer may be that the current work is already the best path and should not change. Do not use for proofreading, encouragement-only feedback, minor style review, or requests where the user only wants implementation.
7test-quality-audit
Audit tests for real bug-finding value. Use when the user asks whether tests are useful, trivial, redundant, over-mocked, implementation-coupled, snapshot-heavy, coverage-padding, only passing because the test controls both sides, or whether tests should be kept, fixed, cut, or added. Also use when reviewing test changes in a PR and the user wants honest judgment about whether the tests earn their place.
7simplify-code-solution
Simplify code fixes and feature proposals by grounding them in real requirements and existing code. Use when a coding plan feels overbuilt, speculative, too abstract, or needs assumptions challenged before implementation.
6