SKILL PLAN · DETERMINISTIC

A small plan for a real job

Start with the minimum useful stack. Add nothing unless it has a clear responsibility in the run.

Task
Frontend build
Agent
Codex
Priority
Balanced
Start over

Rules + reviewed metadata only. No LLM. Same inputs produce the same plan.

03 SKILLS · Install order

Your Skill Plan

Install and verify one role at a time. The plan never forces three Skills when fewer are enough.

Read the public task guide ↗
01Core execution

Native · Codex

frontend-design

Sets the visual direction and implementation constraints.
Open profile and install guide ↗
Review permissions, limitations, and evidence
Agent fit
Native · Codex
Main limitation
Aesthetic judgments remain subjective and still need stakeholder review.
First risk
Style over function · Medium
Source
Pinned source · 0a64e398
02Guardrail

Native · Codex

web-design-guidelines

Checks accessibility, responsiveness, and common interface failures.
Open profile and install guide ↗
Review permissions, limitations, and evidence
Agent fit
Native · Codex
Main limitation
It depends on network access and a live guideline document whose contents can change over time.
First risk
Rule drift or context-free findings · Medium
Source
Pinned source · b8caa260
03Evidence

Native · Codex

playwright-workflows

Produces browser evidence instead of relying on code inspection alone.
Open profile and install guide ↗
Review permissions, limitations, and evidence
Agent fit
Native · Codex
Main limitation
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source
Editorial source

Combined permission budget

This is the union of declared permissions across the plan. Review each package before installation.

Read filesWrite frontend filesRead frontend filesBrowser controlRun commandsWrite screenshots

Finish with evidence

Ship a distinctive interface that still passes practical usability and browser checks.

Frontend files, local preview, and reversible browser checks only.

  1. 3-step acceptance check
  2. Open the changed page at desktop and mobile widths.
  3. Complete the page's primary action with keyboard and pointer input.
  4. Confirm there are no blocking console errors or obvious layout breaks.
  • Stop conditions
  • The plan writes outside the agreed frontend scope.
  • A visual change removes keyboard access or readable contrast.
  • The browser result differs materially from the claimed outcome.