Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is an efficient, code-first conventions sheet with well-organized sections and concrete, near-executable examples for both Next.js and Vite setups. Its main gaps are small: a few incomplete code details (missing imports, undefined helper functions), a redundant intro line and checklist, and no explicit guidance on how to apply the conventions to an existing project.
Suggestions
Make snippets fully self-contained: add the missing `useEffect` import in useUser, type `useState<User | null>(null)`, and note that getUser/fetchUser are placeholders to be replaced by the project's data layer.
Trim the redundant intro sentence and either expand the checklist into concrete verification items (e.g. 'TypeScript strict mode on', 'no default-export pages outside pages/') or remove it.
Add one short 'Como aplicar' section sequencing the guidance (choose framework → scaffold structure → type components → extract hooks) to make application order explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and mostly code, assuming Claude's knowledge of React basics — no padding explaining what React or SSR is. Minor trimmable elements remain: the intro line 'Convenções para React com frameworks modernos.' restates the description, and the closing checklist largely repeats the section headings. Fits anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed'); not 5 because of that small redundancy, not 3 because there is no real over-explanation. | 4 / 5 |
Actionability | Concrete TypeScript/TSX snippets cover the common cases (Next.js page with getServerSideProps, Vite App, typed component, custom hook) and are close to copy-paste ready. Minor gaps keep it from 5: the useUser hook omits the useEffect import, getUser/fetchUser are undefined, and useState(null) lacks a type. Not 3 because the code is real and executable, not pseudocode. | 4 / 5 |
Workflow Clarity | This is a conventions/reference skill, not a multi-step pipeline, so no validation checkpoints are required. Decision guidance is present ('Para projetos que precisam de SEO, SSR ou roteamento' → Next.js; SPA → Vite) and a checklist closes the doc, but applying the conventions to a real project is left implicit. Fits anchor 4; not 5 because there is no explicit sequence for when/how to apply each section. | 4 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent) and the body references no external files, so the skill is a single well-organized file with clear section headers — nothing that clearly belongs in a separate file is inlined. Fits anchor 4 ('Good structure; most content is appropriately placed'); not 5 because the body exceeds the under-50-lines simple-skill case and offers no navigation/signposting beyond flat headings. | 4 / 5 |
Total | 16 / 20 Passed |