agentleFS
NAVANEETHVVINODNAVANEETHVVINOD/agent-orchestrator/skills/project-design/SKILL.md

project-design

Skill0 starsChanged 42 days agoApache-2.0View on GitHub

Plan confirmed project architecture, database/API boundaries and relevant UI/UX flows, pages, wireframes and layouts.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start from confirmed requirements and actual repository constraints.

    line 8

≈ “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

Project Design

Start from confirmed requirements and actual repository constraints. Compare a small set of suitable technical choices using current official documentation; do not select a universal framework/database. Plan component boundaries, auth and permissions, API contracts, schema/relationships/indexes/migrations, state, background work, observability, testing and deployment/rollback as applicable. For a UI application, plan journeys, sitemap/screens, sections/layout/components, responsive behavior, typography/colors, navigation, loading/empty/error/success, validation and accessibility. Use relevant available design skills/tools and inspect resulting wireframes. Non-UI projects do not need artificial pages. Reconcile UX, API and data contracts through the coordinator. Label draft content; do not let fake wireframe behavior silently become shipped functionality. Raise material missing decisions before dependent code. Store canonical narrative design/architecture under docs/ and preserve mandatory loader locations. External design writes or provisioning need authorization for that action.

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.