Borrowing it
Nothing to install: this file belongs to dork-labs/dorkos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dork-labs/dorkos/main/.agents/skills/organizing-fsd-architecture/SKILL.mdgit clone --depth 1 https://github.com/dork-labs/dorkosWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dork-labs/dorkos/organizing-fsd-architecture)<a href="https://agentmods.dev/skills/dork-labs/dorkos/organizing-fsd-architecture"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/organizing-fsd-architecture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dork-labs/dorkos/organizing-fsd-architecture"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/organizing-fsd-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 55 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00055 | $0.01354 |
| Opus 5 | $0.00028 | $0.00677 |
| Sonnet 5 | $0.00011 | $0.00271 |
| Haiku 4.5 | $0.00006 | $0.00135 |
Grade A, and why
organizing-fsd-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organizing FSD Architecture
Overview
This skill provides expertise for implementing Feature-Sliced Design (FSD) in the DorkOS monorepo. FSD organizes code by business domains with clear layer boundaries and unidirectional dependency rules.
The full layer-import matrix, cross-module rules, segment structure, and barrel/alias conventions live in .claude/rules/fsd-layers.md — that rule is the authority; this skill is the placement and size-monitoring guidance on top of it.
When to Use
- Creating new features, widgets, or entities in
apps/client - Deciding where code should live (which layer/segment)
- Reviewing imports for layer violations
- Refactoring components into FSD structure
- Adding new services to
apps/server(size-aware guidance)
The Layer Spine
Strict top-to-bottom dependency flow within apps/client/src/layers/:
app → widgets → features → entities → shared
Higher imports lower, never the reverse; same-level model/hook cross-imports are forbidden (UI composition across features is allowed). See .claude/rules/fsd-layers.md for the per-layer import matrix and code examples.
Step-by-Step: Determine the Correct Layer
Is it a reusable utility, UI primitive (Button, Card), or type?
└─ YES → shared/
Is it a core business entity (Session, Agent, Workspace)?
└─ YES → entities/[entity-name]/
Is it a complete user-facing feature (chat, command palette, settings)?
└─ YES → features/[feature-name]/
Is it a large composition of multiple features (app layout, dashboard)?
└─ YES → widgets/[widget-name]/
Is it app initialization, providers, or entry point?
└─ YES → the src/ root shell (App.tsx, AppShell.tsx, main.tsx, router.tsx)
DorkOS-Specific Layer Mapping
Current shape of apps/client/src/layers/ (representative, not exhaustive — ls the layer for ground truth):
| Layer | Scale | Representative modules |
|---|---|---|
shared/ |
base layer | ui/ (shadcn components), model/ (TransportContext, app-store, useTheme, useIsMobile), lib/ (cn, Transport implementations) |
entities/ |
~14 modules | session, agent, command, marketplace, mesh, relay, runtime, tasks, workspace |
features/ |
~30 modules | chat, command-palette, session-list, settings, marketplace, agents-list, dashboard-*, onboarding |
widgets/ |
~9 modules | app-layout, session, dashboard, agents, marketplace, tasks |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 120 lines · 55 tokens per session scan A 77adee6bc2fd
organizing-fsd-architecture is a skill published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,354 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
design-system
Use when a ticket needs a systematic token + component foundation for a frontend — the three-layer token architecture (primitive → semantic → component), component specs with full state coverage, or a recommendation for which design system a product should have. Invoke for "set up design tokens", "define the component…
frontend-design
Use when a ticket builds or reworks a user-facing frontend surface — a hero, landing page, dashboard, marketing section, or any screen where the visual quality matters, not just the markup. Produces distinctive, intentional, production-grade UI that avoids generic template aesthetics. Invoke for "build the landing…
frontend-foundations
Use on any frontend delivery to hold the surface-specific quality floor that engineering-craft doesn't cover — intentional visual hierarchy over template defaults, accessible-by-default markup, design tokens instead of hardcoded values, reusable components matching the repo, and compositor-friendly motion. Invoke…
landing-page-generator
Use when asked to create a landing page, marketing page, homepage, lead-capture page, campaign page, or conversion-optimised web page. Outputs complete Next.js/React (TSX) + Tailwind CSS components with proven copy frameworks (PAS/AIDA/BAB), SEO meta tags, and Core Web Vitals targets. Triggers on "create a landing…
frontend-component
Use when a ticket asks to add or change a UI component — a new widget, a reusable element, a page section, or a state/variant of one — in a frontend stack. Invoke for "add a Card component", "build the settings panel", or "add a loading state to X". Match the repo's component conventions; do not introduce a new UI…
frontend-responsive
Use when a ticket requires a layout to work across screen sizes — mobile/tablet/desktop, fluid typography, breakpoint behaviour, or fixing overflow and touch-target issues. Invoke for "make X responsive", "fix the mobile layout", "support tablet", or when adding any layout that must adapt.