# Feature Slice Designer

> 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.

- Skill: `conectlens/feature-slice-designer` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add conectlens/feature-slice-designer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/conectlens/feature-slice-designer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: conectlens (https://skillmd.com/u/conectlens)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/conectlens/feature-slice-designer

---


# 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](references/REFERENCE.md)
- [Feature plan template](assets/feature-plan-template.md)