Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/plugin87/full-stack-design-skills/frontend-framework-guidenpx skills add plugin87/full-stack-design-skills --skill frontend-framework-guidegit clone --depth 1 https://github.com/plugin87/full-stack-design-skillsWhat 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 | $0.00103 | $0.03307 |
| Opus 5 | $0.00051 | $0.01654 |
| Sonnet 5 | $0.00021 | $0.00661 |
| Haiku 4.5 | $0.00010 | $0.00331 |
Grade A, and why
frontend-framework-guide 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 2d 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 — 606 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Framework Guide
Patterns and best practices for building production applications with modern frameworks, primarily React.
React is the dominant frontend framework for building scalable applications. Mastering React's mental model—component composition, hooks, state management, and performance optimization—is essential for professional development.
Core Concept: Components & Composition
The React Mental Model
React is built on declarative component composition:
State → Component → UI
User interaction → State change → Re-render → New UI
Declarative: Describe what UI should look like, React handles updates. Imperative: Manually update DOM (old way, error-prone).
Functional Components (Modern)
function Button({ label, onClick }) {
return (
<button onClick={onClick}>
{label}
</button>
);
}
// Use it
<Button label="Click me" onClick={() => console.log('clicked')} />
Functional components are the standard now. Class components are legacy.
Hooks: The Foundation
useState: Managing Component State
import { useState } from 'react';
function Counter() {
const [count, setCount] = useState(0);
// count: current state value
// setCount: function to update state
return (
<div>
<p>Count: {count}</p>
<button onClick={() => setCount(count + 1)}>
Increment
</button>
</div>
);
}
Key points:
useStatereturns[value, setter]- Setter triggers re-render
- Initial value can be a function (useful for expensive calculations)
useEffect: Side Effects
import { useEffect, useState } from 'react';
function DataFetcher() {
const [data, setData] = useState(null);
const [loading, setLoading] = useState(true);
useEffect(() => {
// Run after render
fetch('/api/data')
.then(res => res.json())
.then(data => {
setData(data);
setLoading(false);
});
}, []); // Dependency array: run once on mount
if (loading) return <div>Loading...</div>;
return <div>{data}</div>;
}
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 606 lines · 0 tokens per session scan A ad89ff88ff79
frontend-framework-guide is a skill published in the GitHub repository plugin87/full-stack-design-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 3,307 once invoked, about $0.0005 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
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
row-selection
Maintain rowSelection ID state with stable getRowId, single, multi, subrow, and Shift-range rules, selected row models, handler anchors, and manual-pagination semantics. Load when implementing getToggleSelectedHandler, enableRowRangeSelection, selectChildren, deselectParents, or selected IDs that outlive loaded Row…
flags
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.