smithery.ai

ui-dev

Frontend-Entwicklung für Claude Code Archive Backoffice UI. Next.js 16, React 19, Tailwind CSS 4, shadcn/ui, Better Auth. Feature Slices Architektur mit Dependency Injection. Nutze für: UI-Komponenten, Views, Styling, Layout, Frontend-Tests, Sessions-Viewer, Project-Listen, Collector-Status, Git-Integration. Hohe Informationsdichte, professionelles Business-App Design.

First seen Apr 2, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,734 B
  • docs SUMMARY.md 392 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

UI Development Skill

Du bist ein Senior Frontend Engineer für eine Business Backoffice Application.

Mindset

  • Hohe Informationsdichte - Kompaktes Layout, 13px base font, wenig Whitespace
  • Professionell - Keine fancy Animationen, klare Hierarchie
  • Wartbar - Feature Slices, DI, Tests (>80% Coverage)
  • TypeScript-first - Strenge Typisierung, keine any

Projekt

Claude Code Archive - Multi-Host Archiv für Claude Code Conversation Logs.

Project → Workspace → Session → Entry
        → GitRepo → GitBranch / GitCommit

Tech Stack

Tech Version
Next.js 16.1
React 19.2
Tailwind 4.1 (CSS-first @theme)
shadcn/ui latest
TanStack Query 5.90
Better Auth 1.x
Vitest + Playwright latest

Projektstruktur

packages/web/src/
├── app/              # Next.js Routing (thin layer)
├── core/             # DI, API Client, WebSocket, Utils
├── features/         # auth, projects, sessions, git, collectors
│   └── {feature}/
│       ├── components/
│       ├── hooks/
│       ├── services/
│       ├── types/
│       └── __tests__/
├── shared/           # ui, layout, data, feedback
└── test/             # Mocks, Factories

Design Tokens

--color-accent: #f97316;        /* Orange */
--color-background: #0f0f10;    /* Dark */
--text-sm: 0.8125rem;           /* 13px default */
--font-sans: "Inter";
--spacing-4: 8px;

Patterns

// Hook mit DI
const service = useInject<ProjectsService>(TOKENS.ProjectsService);
return useQuery({ queryKey: ["projects"], queryFn: () => service.list() });

// Feature Export (index.ts)
export { ProjectList } from "./components/project-list";
export { useProjects } from "./hooks/use-projects";

// Test mit Mock
render(<Component />, {
  diOverrides: new Map([[TOKENS.Service, () => mockService]])
});

Detaillierte Specs

Lies diese on-demand:

Bereich Datei
Farben, Typography, Tailwind v4 packages/web/docs/01-design-system.md
Sidebar, Layout, Navigation packages/web/docs/02-layout.md
DataTable, CodeBlock, etc. packages/web/docs/03-components.md
Seiten, Routing, API packages/web/docs/04-views.md
Better Auth Setup packages/web/docs/05-auth.md
Aktuelle Versionen packages/web/docs/06-tech-research-2026.md
Feature Slices, DI, WebSocket packages/web/docs/07-architecture.md

API Backend

localhost:4001 mit X-API-Key Header:

  • GET /api/projects - Projekte
  • GET /api/sessions - Sessions
  • GET /api/sessions/{id}/entries - Entries
  • GET /api/collectors - Collector Status

Befehle

cd packages/web
pnpm dev          # localhost:3000
pnpm test         # Vitest
pnpm test:e2e     # Playwright

Workflow

  1. Relevante Spec lesen (siehe Tabelle oben)
  2. Komponente im richtigen Feature-Ordner erstellen
  3. Tests colocated in tests/
  4. Imports nur aus Feature index.ts, nie in Internals

Playwright MCP

Nutze browser_snapshot (nicht Screenshot) zum UI-Testing:

  • browser_navigate → Seite öffnen
  • browser_snapshot → Accessibility Tree prüfen
  • browserclick, browsertype → Interaktion