agentleFS
conectlensconectlens/lenserfight/.agents/skills/feature-slice-designer/SKILL.md

feature-slice-designer

Skill18 starsChanged 6 months agoMITView on GitHub

Decide where new behavior belongs across apps, features, domain, data, api, ui, infra, and utils. Use before implementing a feature, refactor, or cross-layer change in the LenserFight monorepo.

The file

Files
SKILL.md

Feature Slice Designer

Use when

  • a new feature spans multiple layers
  • the correct target library is unclear
  • scope must be decomposed before implementation

Workflow

  1. Translate the request into domain, data, UI, and integration responsibilities.
  2. Assign each responsibility to the correct library or create a justified new boundary.
  3. Return a file-level implementation plan, public APIs, and constraints.

Load only when needed

  • Placement rules
  • Feature plan template

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.