agentleFS
RostislavDuginRostislavDugin/postgresus/.agents/skills/feature-sliced-design/SKILL.md

feature-sliced-design

Skill9.3k starsChanged 6 days agoApache-2.0View on GitHub

Place or reorganize Databasus frontend code across layers and slices, define public APIs, and repair forbidden imports. Use for frontend architecture and ownership decisions; ordinary copy or style changes alone do not need this skill.

5 other projects use a version of this.

Trending

Quiet since July.thin dataabout the whole repository

Dec 2025: 4 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the RostislavDugin/postgresus repository that our weekly crawl found: only 10 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about RostislavDugin/postgresus

The biggest 5 of 10 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 10

Talked about on GitHub and Bluesky (10 times).

On GitHub · 7

2 more on GitHub

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Read the Frontend section of architecture.md and the local conventions in frontend/AGENTS.md before changing placement or dependencies.

    line 8
  2. Distinctive:

    Check the affected consumers and public entry points before a move.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

Frontend boundaries

Read the Frontend section of architecture.md and the local conventions in frontend/AGENTS.md before changing placement or dependencies. Those project rules take precedence over the upstream methodology, including its alternatives for domain API placement, widgets, cross-imports and decision records.

Use the vendored FSD methodology to investigate placement and dependency problems. Load its conditional references only when the task needs them. Start with the closest real consumer, identify the responsibility that changes independently, and choose the smallest boundary that owns it. Follow the project's architecture when an upstream alternative differs.

Check the affected consumers and public entry points before a move. Keep mechanical moves separate from changes in behavior, preserve scenario coverage, and run frontend lint, relevant tests and the production build. A forbidden dependency has no exception: repair it.

The upstream text and references are vendored verbatim from Feature-Sliced Design contributors. upstream.json records the source revision, license declaration and content hashes; LICENSE contains the MIT terms. Keep attribution and the full source revision when updating those files.

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.