Skills project-architecture

📦

project-architecture

Name: project-architecture
Author: c3sc0-v4113

v1.0 Content revision r1 Safe ⚙️ External commands

Keep Next.js and Astro Changes Server-First

UI changes can introduce unnecessary browser code and inconsistent component boundaries. This skill guides framework detection, server-first implementation, explicit data states, and documented boundary decisions.

Supports: Claude Codex Code(CC)

📊 74 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "project-architecture" from https://skillstore.io/skills/c3sc0-v4113-project-architecture.md and its manifest at https://skillstore.io/api/skills/c3sc0-v4113-project-architecture/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.

Markdown detail GET /skills/c3sc0-v4113-project-architecture.md Signed manifest GET /api/skills/c3sc0-v4113-project-architecture/manifest Signed lockfile GET /api/skills/c3sc0-v4113-project-architecture/lockfile

Test it

Using "project-architecture". Add a collapsible details panel to a Next.js page.

Expected outcome:

Framework: Next.js, identified from project dependencies.
Boundary change: only the details toggle needs client state; the page and data fetching remain server-rendered.
Checklist: client code is limited to the interaction, existing design conventions are preserved, and applicable data states are explicit.

Using "project-architecture". Add an interactive calculator below static content in an Astro page.

Expected outcome:

Framework: Astro, identified from project configuration.
Boundary change: add one small React island for calculator input; surrounding content remains server-rendered.
Hydration: use visibility-based hydration because the calculator is below the initial viewport.
Checklist: no other client boundary is added; styling follows project guidance; applicable loading, empty, and error states are explicit.

Security Audit

Safe

v1 • 10/2/2026 Open versioned report

All eight static findings are false positives: seven match Markdown inline formatting, and one matches a UI boundary checklist question. No evidence found of prompt injection, credential access, data exfiltration, or malicious execution in the reviewed files. The workflow includes ordinary project inspection and quality scripts, which should run only in trusted projects.

Files scanned

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (7)

SKILL.md:21 SKILL.md:22 SKILL.md:30 SKILL.md:31 SKILL.md:36 SKILL.md:40 SKILL.md:45

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex

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.

Open versioned report

Copy report link

https://skillstore.io/skills/c3sc0-v4113-project-architecture/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/c3sc0-v4113-project-architecture/security.svg)](https://skillstore.io/skills/c3sc0-v4113-project-architecture?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/c3sc0-v4113-project-architecture?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/c3sc0-v4113-project-architecture/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/c3sc0-v4113-project-architecture.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

c3sc0-v4113. (2026). project-architecture security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/c3sc0-v4113-project-architecture/audits/1

BibTeX citation

@techreport{c3sc0-v4113-c3sc0-v4113-project-architecture-2026,
  author = {c3sc0-v4113},
  title = {project-architecture security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/c3sc0-v4113-project-architecture/audits/1},
  note = {Author version 1.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "project-architecture security audit report (audit version 1)"
version: "1.0"
type: report
authors:
  - name: "c3sc0-v4113"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/c3sc0-v4113-project-architecture/audits/1"
identifiers:
  - type: other
    value: "skillstore:c3sc0-v4113-project-architecture:audit:1"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

AbdulSamad94 Recommended

abdulsamad94-project-architecture

Skillstore Score 76

Evidence Confidence High

Skillstore usage 12

Updated

2026-09-09

c3sc0-v4113 Current

c3sc0-v4113-project-architecture

Skillstore Score 74

Evidence Confidence Medium

Skillstore usage Unknown

Updated

2026-10-03

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Add an Interactive Next.js Component

Keep page rendering and data fetching on the server while isolating a small interactive component.

Choose Astro Island Boundaries

Separate static content from interactive widgets and select hydration directives based on interaction needs.

Review UI Architecture Changes

Check framework evidence, design consistency, data states, and reasons for new client boundaries before closing a change.

Try These Prompts

Identify the Framework

Use project-architecture to inspect this project and identify its framework. Report the evidence and ask for clarification if it is ambiguous.

Make a Small UI Change

Use project-architecture to add an empty state to this data display. Follow existing design conventions and report any server/client boundary changes.

Add a Minimal Interactive Boundary

Use project-architecture to add a filter to this list. Keep rendering server-first, isolate necessary interaction, and test loading, empty, and error states.

Refactor a Broad Client Boundary

Use project-architecture to refactor this page for server-first rendering. Explain each boundary change, preserve behavior, and run reviewed project quality checks.

Best Practices

Confirm the target framework and consult documentation matching the installed version before changing framework APIs.
Keep interaction boundaries small and pass serializable props from server-rendered parents.
Review project quality scripts before running them, then document boundary reasons and checklist results.

Avoid

Marking an entire page as client-rendered when only one small control needs interaction.
Hydrating every Astro island immediately without evaluating visibility or idle hydration.
Creating custom components before checking existing primitives, semantic tokens, and project design guidance.

Frequently Asked Questions

Which frameworks does this skill cover?

It provides specific architecture guidance for Next.js and Astro.

How does it identify the framework?

It checks dependencies and root configuration files. If both frameworks appear or neither is detected, it asks which app the change targets.

Does it prohibit client-side JavaScript?

No. It allows client code for necessary interaction and keeps the client boundary as small as possible.

Does it require shadcn or companion skills?

It prioritizes existing shadcn primitives and loads companion skills when installed. It does not include an installation workflow.

Does it run project checks?

The workflow requests an installed evaluation skill or project quality scripts. Review scripts before execution because project-defined commands can run code.

What should the final report include?

The detected framework, every server/client boundary added or moved, the reason for each change, and checklist answers.