Skills project-structure

📦

project-structure

Name: project-structure
Author: Doyajin174

v1.0 Content revision r1 Safe ⚙️ External commands🌐 Network access📁 Filesystem access

Organize Project Structure

Messy repositories make navigation, ownership, and refactoring harder. This skill provides safe folder layouts and cleanup workflows for JavaScript and frontend projects.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

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-structure" from https://skillstore.io/skills/doyajin174-project-structure.md and its manifest at https://skillstore.io/api/skills/doyajin174-project-structure/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/doyajin174-project-structure.md Signed manifest GET /api/skills/doyajin174-project-structure/manifest Signed lockfile GET /api/skills/doyajin174-project-structure/lockfile

Test it

Using "project-structure". I need a folder plan for a new Next.js dashboard.

Expected outcome:

Recommended route groups for public and dashboard pages.
Shared components stay separate from route-specific components.
Global utilities belong in lib, hooks, and types.

Using "project-structure". My React project has many components and hooks in top-level folders.

Expected outcome:

Suggested a feature-based layout for auth, users, and dashboard areas.
Moved obsolete folders to a dated _legacy area in the plan.
Highlighted checks to run before applying moves.

Using "project-structure". Our team is choosing between Bulletproof React and Feature-Sliced Design.

Expected outcome:

Compared team size, domain complexity, and rule overhead.
Recommended the lighter feature-based pattern for faster adoption.
Listed migration risks and naming standards.

Security Audit

Safe

v8 • 7/5/2026 Open versioned report

The static scan reported command, network, filesystem, and sensitive-file patterns, but review found them in Markdown examples, folder diagrams, and reference links. The command guidance uses hardcoded setup or move examples and explicitly forbids deletion in favor of _legacy. No prompt injection, data exfiltration, or malicious intent was found.

Files scanned

354

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (47)

🌐 Network access (3)

SKILL.md:351 SKILL.md:352 SKILL.md:353

📁 Filesystem access (4)

SKILL.md:305 SKILL.md:306 SKILL.md:311 SKILL.md:330

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 View Audit History →

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/doyajin174-project-structure/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

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

Doyajin174. (2026). project-structure security audit report (audit version 8) [Author version 1.0]. Skillstore. https://skillstore.io/skills/doyajin174-project-structure/audits/8

BibTeX citation

@techreport{doyajin174-doyajin174-project-structure-2026,
  author = {Doyajin174},
  title = {project-structure security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/doyajin174-project-structure/audits/8},
  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-structure security audit report (audit version 8)"
version: "1.0"
type: report
authors:
  - name: "Doyajin174"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/doyajin174-project-structure/audits/8"
identifiers:
  - type: other
    value: "skillstore:doyajin174-project-structure:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Set up a new frontend project

Create a clear starting layout for a React or Next.js application before source files grow.

Clean a messy repository

Move outdated folders into _legacy and reshape source files around features or routes.

Standardize team conventions

Compare common architecture patterns and document a shared folder strategy for contributors.

Try These Prompts

Create a starter structure

Use the project-structure skill to propose folders for a new React app. Explain why each top-level folder exists.

Reorganize a messy repository

Review this repository structure and suggest a safer layout. Move obsolete items to _legacy instead of deleting anything.

Choose an architecture pattern

Compare Next.js colocation, Bulletproof React, and Feature-Sliced Design for this product. Recommend one folder strategy with tradeoffs.

Plan a staged migration

Create a staged migration plan from type-based folders to feature-based folders. Include file move groups, checks, and rollback notes.

Best Practices

Review every move command before running it against a real repository.
Choose one primary grouping rule, such as route, feature, or domain.
Keep removed or uncertain code in dated _legacy folders until reviewed.

Avoid

Running deletion commands during structure cleanup.
Mixing work, personal, and study projects in one unlabeled folder.
Putting every component, hook, and utility into global type-based folders.

Frequently Asked Questions

Does this skill delete files?

No. The guidance explicitly forbids deletion and recommends moving old items into _legacy.

Which project types fit best?

It fits frontend and full-stack JavaScript projects, especially React and Next.js codebases.

Can it organize monorepos?

It can suggest high-level folder boundaries, but it does not provide a full monorepo package strategy.

Does it create files automatically?

It includes command examples for folders and starter files. Users should review paths before execution.

Does it require internet access?

No for local organization. Internet access is only needed to open the listed reference links.

Can Claude Code or Codex use it?

Yes. The metadata lists Claude, Codex, and Claude Code as supported tools.

Developer Details

Author

Doyajin174

License

MIT

Author version

v1.0

Skillstore revision

Version notice

The author-declared version is not valid SemVer.

Repository

https://github.com/Doyajin174/myskills/tree/main/.public/skills/project-structure

Ref

c579efd02184f1128d6741d16e6c8d951d7d4208

Maintenance freshness

7/18/2026

Usage

4 downloads · 266 views

File structure

📄 SKILL.md