frontend-dev-guidelines
Build Next.js Frontends With Shared Guidelines
Frontend teams need consistent React and Next.js patterns across pages, components, forms, and data fetching. This skill provides practical guidance for shadcn/ui, Tailwind, Supabase, routing, performance, and TypeScript.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "frontend-dev-guidelines" from https://skillstore.io/skills/dojocodinglabs-frontend-dev-guidelines.md and its manifest at https://skillstore.io/api/skills/dojocodinglabs-frontend-dev-guidelines/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "frontend-dev-guidelines". Create a profile page with server data and a loading state.
Expected outcome:
A concise implementation plan with route placement, data fetching choice, metadata needs, loading UI, and component responsibilities.
Using "frontend-dev-guidelines". Review a React form for consistency with the guidelines.
Expected outcome:
A focused checklist covering validation, controlled fields, submit handling, error display, and reusable shadcn/ui components.
Using "frontend-dev-guidelines". Improve a slow route that loads charts and tables.
Expected outcome:
Recommendations for lazy loading heavy components, placing Suspense boundaries, memoizing expensive values, and avoiding unnecessary client components.
Security Audit
SafeAll 153 static findings are adjudicated as false positives. The flagged items are Markdown examples or TypeScript and React patterns such as dynamic imports, template literals, relative imports, axios examples, same-origin fetches, and UI grid text. No prompt injection, data exfiltration intent, shell execution, or unsafe filesystem behavior was found in the reviewed skill content.
Risk Factors
โก Contains scripts (19)
โ๏ธ External commands (45)
๐ Filesystem access (28)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dojocodinglabs-frontend-dev-guidelines/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dojocodinglabs-frontend-dev-guidelines?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dojocodinglabs-frontend-dev-guidelines?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dojocodinglabs-frontend-dev-guidelines/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dojocodinglabs-frontend-dev-guidelines.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
DojoCodingLabs. (2026). frontend-dev-guidelines security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dojocodinglabs-frontend-dev-guidelines/audits/8BibTeX citation
@techreport{dojocodinglabs-dojocodinglabs-frontend-dev-guidelines-2026,
author = {DojoCodingLabs},
title = {frontend-dev-guidelines security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/dojocodinglabs-frontend-dev-guidelines/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "frontend-dev-guidelines security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "DojoCodingLabs"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dojocodinglabs-frontend-dev-guidelines/audits/8"
identifiers:
- type: other
value: "skillstore:dojocodinglabs-frontend-dev-guidelines:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
7 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
briandai22-frontend-dev-guidelines
2026-09-09
0chan-smc-frontend-dev-guidelines
2026-09-09
bom-98-frontend-dev-guidelines
2026-09-09
sickn33-frontend-dev-guidelines
2026-09-09
dojocodinglabs-frontend-dev-guidelines
2026-09-09
dimon94-frontend-dev-guidelines
2026-09-09
diet103-frontend-dev-guidelines
2026-09-09
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Create Feature Pages
Use the guidelines to build pages with data fetching, loading states, errors, and typed component structure.
Standardize Frontend Architecture
Use the conventions to align teams on folders, components, imports, forms, and data layer patterns.
Guide AI Frontend Changes
Give Claude, Codex, or Claude Code clear implementation rules for Next.js and React tasks.
Try These Prompts
Use the frontend-dev-guidelines skill to create a Next.js App Router page for a dashboard list. Include loading, error, metadata, and typed props.
Use the frontend-dev-guidelines skill to design a React Hook Form with Zod validation and shadcn/ui fields. Explain the component boundaries.
Use the frontend-dev-guidelines skill to refactor this feature from client-side fetching to safer Server Components or TanStack Query patterns.
Use the frontend-dev-guidelines skill to plan a complete feature module with routes, components, API helpers, loading states, errors, and TypeScript types.
Best Practices
- Use Server Components by default and add client components only for hooks, browser APIs, or events.
- Keep forms typed with React Hook Form, Zod schemas, and clear validation messages.
- Add loading, error, and Suspense boundaries close to the data or component that needs them.
Avoid
- Adding use client to every component without a browser-only need.
- Creating ad hoc UI instead of using the shared shadcn/ui and Tailwind patterns.
- Fetching server data into client state when a Server Component or query cache fits better.
Frequently Asked Questions
Which projects fit this skill best?
Can I use it without Supabase?
Does it write production code automatically?
Does it support Claude Code and Codex?
Does it include accessibility testing?
Why are there MUI examples in a shadcn/ui skill?
Developer Details
Author
DojoCodingLabsLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
72d5025b022c77f7a51bdf5c1637c689c80e89d1
Maintenance freshness
7/18/2026
Usage
6 downloads ยท 270 views
File structure
๐ resources/
๐ common-patterns.md
๐ complete-examples.md
๐ data-fetching.md
๐ file-organization.md
๐ loading-and-error-states.md
๐ performance.md
๐ routing-guide.md
๐ styling-guide.md
๐ SKILL.md