nextjs-cursorrules
Provides coding standards and best practices for building Next.js applications with Tailwind CSS through a structured cursor rules file.
92
/ 100 · Grade A
A = 90–100
“I need to establish consistent coding conventions and best practices for my Next.js and Tailwind CSS development workflow.”
nextjs-cursorrules earned Certified status with a trust score of 92/100 (Grade A). No adversarial findings — all attack patterns were handled gracefully. Security scan flagged 0 findings.
Trust Score Breakdown
Eight weighted signals composing the aggregate trust score
Scheme v2.0 · Weights provisional · Consumer confirmations and uptime use pipeline-derived baselines.
Findings
Security scan results, adversarial testing, and pipeline review
Security Scan — Cisco Skill Scanner
Adversarial Testing — 5 categories, 0 findings
No adversarial findings — all attack patterns handled gracefully.
Methodology v1.0 · 5 categories · ~55 attack patterns
Behavioral Fingerprint
Runtime performance baseline for drift detection
Samples
8
Error rate
0.0%
Peak memory
— MB
Avg CPU
—%
Response time distribution
Output size distribution
Fingerprint v1.0 · Baseline: Mar 28, 2026 · Status: baseline
Interface
Skill triggers and instruction summary
Activation
This skill activates when developers need coding conventions and best practices for Next.js projects with TypeScript, React, and Tailwind CSS.
This skill handles providing structured guidelines for Next.js project organization, coding standards, and architectural patterns.
Does
Provide coding conventions for TypeScript projects
Recommend functional and declarative programming patterns
Suggest descriptive naming conventions
Guide on Next.js App Router usage
Recommend Shadcn UI and Tailwind CSS best practices
Advise on component organization by type or feature
Promote server components over client components for performance
Suggest /src directory structure for projects
Does not
Recommend using enums in TypeScript
Suggest excessive client-side interactions
Promote unorganized file structures
Recommend types over interfaces in TypeScript
Scope & Permissions
What this capability can and cannot access — derived from pipeline analysis
no
no
no
no
no
no
Known Failure Modes
Documented edge cases and recovery behaviors
when when asked about non-Next.js frameworks
then the agent should clarify this skill is specific to Next.js projects
when when asked to generate actual code files
then the agent provides guidance and examples but doesn't create files
Badge & Integration
Embed certification status in your README, docs, or CI pipeline
Certification Notes
Provenance observations from the pipeline
Skill metadata extraction confidence is 75% — review extracted triggers, scope, and behavioral guarantees
Publisher "PatrickJS" is not verified — first certification from this publisher
No SECURITY.md or SECURITY.txt file found — no published vulnerability reporting process
Single contributor — no peer review evidence in commit history
Package description appears to be boilerplate or template text
Signed Artifact
Certification provenance and verification metadata
Pipeline Artifacts
Raw data files from this certification run — downloadable for independent verification
contract.json
Full unsigned contract
stage1-ingest.json
Ingest stage output
stage2a-sbom.json
SBOM generation results
stage2a-vulns.json
Vulnerability scan results
stage2b-security.json
Security scan results
stage3a-functional.json
Functional test results
stage3b-adversarial.json
Adversarial test results
stage3c-fingerprint.json
Behavioral fingerprint
stage4-certify.json
Certification decision + trust score
stage3a-measurements.json
Raw functional test measurements
stage3b-measurements.json
Raw adversarial test measurements
run-log.json
Pipeline execution log
Not all files may be present for every certification.