component-organization
Frontend Component Organization
This is a reference pattern. Learn from the approach, adapt to your context — don't copy verbatim.
Problem: Frontend projects grow into disorganized directories where related files are hard to find and shared code has no clear home.
Solution: Organize by type (components, hooks, lib, types), with subdirectories for grouping related items within each type.
Pattern
frontend/
├── app/ # Framework routing (Next.js app dir, Nuxt pages, etc.)
│ ├── layout.tsx
│ └── page.tsx
├── components/ # All components
│ ├── ui/ # Base primitives (Button, Input, Modal)
More from loxosceles/ai-dev
static-frontend-hosting
S3 + CloudFront + Lambda@Edge for low-cost global hosting with edge authentication. Apply when setting up frontend hosting infrastructure.
64github-actions-oidc-aws
Secure GitHub Actions to AWS authentication using OIDC without long-lived credentials. CRITICAL PATTERN. Apply when setting up CI/CD pipelines that deploy to AWS.
53code-review
Multi-perspective code review strategy covering architecture, security, performance, and quality. Follow when reviewing code or analyzing changes.
51frontend-code-quality
Essential guidelines for clear, maintainable frontend code. Follow when writing or reviewing frontend components, composables, or pages.
51command-execution
Guidelines for executing commands and running scripts. Follow when running shell commands, installing packages, or using project scripts.
51cdk-bootstrap-configuration
CDK synth-time configuration pattern without context caching. Apply when working on CDK infrastructure code or adding new configuration parameters.
50