# Navigate DevPrep AI Architecture

Large feature work often slows down when developers do not know where code belongs. This skill maps the DevPrep AI folder structure and recommends precise locations for new code.

## Install

```bash
npx skillstore add ariegoldkin/architecture-navigator
```

## Metadata

- - Slug: ariegoldkin-architecture-navigator
- - Version: 1.0.0
- - Author: ArieGoldkin
- - GitHub username: ArieGoldkin
- - License: MIT
- - Repository: https://github.com/ArieGoldkin/devPrepAi/tree/main/.claude/skills/architecture-navigator
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: scripts, external\_commands, filesystem
- - Quality score: 50
- - Quality tier: warning
- - Public page: https://skillstore.pages.dev/skills/ariegoldkin-architecture-navigator
- - Manifest: https://skillstore.pages.dev/api/skills/ariegoldkin-architecture-navigator/manifest

## Capabilities

- Explains the DevPrep AI 7-folder structure and each folder purpose.
- Recommends exact paths for new routes, modules, shared components, stores, types, and integrations.
- Runs or describes a local scanner that summarizes modules, files, and key source locations.
- Checks placement decisions against documented import direction rules.
- Identifies common architecture drift such as business logic in route files.
- Provides examples for authentication, payments, UI components, state, API types, and styling.

## Use Cases

- Place a New Feature: Decide whether a new capability belongs in modules, shared, lib, store, types, styles, or app.
- Review Architecture Drift: Check whether routes, imports, and shared components still follow the documented project boundaries.
- Onboard to DevPrep AI: Understand the existing source layout before making a first change or reviewing a pull request.

## Prompt Templates

### Find the Right Folder

```
Where should I add a new notification toast feature in the DevPrep AI architecture? Explain the folder choice.
```

### Scan Current Structure

```
Scan the current DevPrep AI architecture and summarize the modules, shared components, state, and app routes.
```

### Validate a Planned Change

```
I plan to add payment processing with UI, API client code, and global checkout state. Tell me where each part belongs.
```

### Audit Import Boundaries

```
Review this feature plan against the DevPrep AI import rules. Flag cross-module imports, app logic, and misplaced shared code.
```

## Limitations

- Designed for the DevPrep AI architecture, not a general framework standard.
- The scanner depends on a frontend/src layout and may miss differently named folders.
- It provides placement guidance, but it does not refactor code automatically.
- It may run local shell commands when the user or agent requests architecture scanning.

## Best Practices

- Scan the current architecture before making placement recommendations.
- Give exact target paths and the rule that supports each path.
- Warn users before running local shell commands in a workspace.

## Anti Patterns

- Do not put business logic directly in app route files.
- Do not create cross-module imports between feature folders.
- Do not move code into shared before it has a real second use.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T10:40:49.622\+00:00
- - Summary: Static analysis flagged many shell, weak-crypto, and reconnaissance patterns. Review found most markdown hits are false positives from code fences, folder names, and examples, but the skill does include a bash scanner that enumerates local project files. No evidence found of prompt injection, network exfiltration, credential access, or malicious intent.

## Stats

- - Views: 184
- - Downloads: 4
- - Favorites: 1
- - Popularity score: 0