Framework-agnostic frontend architecture — state management, components, data fetching. Use when building any web frontend, choosing state patterns, or structuring UI code.
Install with Tessl CLI
npx tessl i github:ravnhq/ai-toolkit --skill platform-frontend67
Quality
51%
Does it follow best practices?
Impact
95%
1.10xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/platform/platform-frontend/SKILL.mdServer vs client state separation
Query library for server state
100%
100%
No API data in client store
100%
100%
Client store for UI state only
100%
100%
Loading state handled
75%
100%
Error state handled
62%
100%
Empty state handled
12%
100%
Local state before lifting
100%
100%
Named exports used
100%
100%
No barrel files
100%
100%
No premature memoization
100%
100%
Feature-based organization
20%
0%
Without context: $0.6469 · 2m 48s · 33 turns · 40 in / 9,907 out tokens
With context: $0.7400 · 2m 39s · 36 turns · 37 in / 9,190 out tokens
Component single responsibility and composition
Split by responsibility
100%
100%
No monolithic component
100%
100%
Composition over props
100%
100%
Props for variants only
100%
100%
Loading state present
62%
75%
Error state present
50%
100%
Empty state present
62%
75%
Link component for internal nav
0%
100%
Anchor tag for external links
100%
100%
Named exports
100%
100%
No barrel files
100%
100%
Without context: $0.4442 · 3m 5s · 27 turns · 34 in / 6,255 out tokens
With context: $0.7277 · 2m 25s · 39 turns · 1,651 in / 9,715 out tokens
No barrel files and feature-based organization
Feature-based directory structure
100%
100%
No index.ts barrel files
100%
100%
Direct file imports
100%
100%
Named exports only
100%
100%
No unjustified memoization
100%
100%
Local state before global
100%
100%
File tree documented
100%
100%
Import examples provided
100%
100%
Consistent naming
100%
100%
Without context: $0.3055 · 1m 40s · 17 turns · 24 in / 4,895 out tokens
With context: $0.6371 · 2m 2s · 33 turns · 635 in / 7,556 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.