agentleFS
Sign inStart free
flightctlflightctl/ai-workflows/ui-implement/SKILL.md

ui-implement

Skill10 starsChanged 21 days agoMITView on GitHub

Story-to-code workflow for UI/front-end stories. Takes a Jira [UI] Story, plans the implementation using discovered design-system and testing conventions, writes contract-based unit tests and production code via TDD, validates against the project's CI expectations, and manages review via GitHub PRs. Use when implementing [UI] stories produced by the design workflow with a ui-design document. Activated by commands: /ingest, /plan, /revise, /code, /validate, /publish, /respond.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user invoked a specific command (e.g., /plan, /code), read the matching file in commands/ and follow it.

    line 17
  2. Very specific:

    If the user provided a Jira issue key or URL, execute the /ingest phase

    line 20
  3. Distinctive:

    If a step fails or produces unexpected output (e.g., Jira MCP errors, test failures, build errors), stop and report the error to the user.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UI Implement Workflow Orchestrator

Quick Start

  1. If the user invoked a specific command (e.g., /plan, /code), read the matching file in commands/ and follow it.
  2. Otherwise, read skills/controller.md to load the workflow controller:
    • If the user provided a Jira issue key or URL, execute the /ingest phase
    • Otherwise, execute the first phase the user requests

If a step fails or produces unexpected output (e.g., Jira MCP errors, test failures, build errors), stop and report the error to the user. Do not advance to the next phase. Offer to retry the failed step or escalate.

For principles, hard limits, safety, quality, and escalation rules, see guidelines.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free