01
TECH STACK DECLARATION
The literal inventory of your technology choices. The F3-Framework needs version-specific details because defaults change dramatically between versions.
Framework & Version
Language & Version
CSS / Styling Methodology
State Management
Database & ORM
Authentication Approach
Package Manager
Build Tooling
Additional Key Dependencies
Guardrail: The F3-Framework ensures Claude never suggests or introduces a technology not on this list without explicitly flagging it as an addition.
02
FOLDER STRUCTURE MAP
The exact directory layout. This is one of the biggest friction points — without the F3-Framework, Claude defaults to the framework's generic structure, not yours.
Primary Source Directory Structure (2-3 levels deep)
Where do shared/reusable components live?
Where do feature-specific modules live?
Where do utilities and helpers live?
Where do types/interfaces live?
Where do API-related files live?
Any other key directories?
Guardrail: The F3-Framework ensures Claude never creates files outside this structure or new top-level directories without explicit instruction.
03
NAMING CONVENTIONS
How things are named. This prevents the most invisible damage — code that works but doesn't match your codebase style.
File Naming Convention
Component Naming
Function / Method Naming
CSS Class Naming
Variable Naming
Database Table / Column Naming
API Endpoint Naming
Test File Naming
Guardrail: Every generated file, function, variable, and class name should be indistinguishable from code the developer wrote themselves.
04
ARCHITECTURAL PATTERNS
How things connect. Two developers can use the exact same stack and build completely differently based on architecture.
Overall Architecture Pattern
Data Flow Description
Separation of Concerns
API Layer Design
Error Handling Strategy
Cross-Cutting Concerns
Guardrail: The F3-Framework ensures Claude follows your established data flow and separation of concerns, never mixing layers you keep separate.
05
COMPONENT & MODULE PATTERNS
The internal anatomy of a typical file — how components and modules are structured internally, beyond just naming.
Component Structure
Props / Types Pattern
Export Pattern
Loading / Error / Empty States
Template or Boilerplate Patterns
Guardrail: Generated components should follow the internal structure of existing components so they feel native to the codebase.
06
STYLING RULES
Deceptively complex — styling approaches vary enormously and without the F3-Framework, Claude's defaults almost never match a specific project.
Design Tokens / Theme Variables
Responsive Breakpoint Strategy
Component Styling Pattern
Animation / Transition Conventions
Dark Mode Approach (if applicable)
UI Component Library (if any)
Guardrail: The F3-Framework ensures Claude never introduces inline styles if you use CSS Modules, nor arbitrary Tailwind values if you have a defined design system.
07
STATE MANAGEMENT APPROACH
How data is stored, shared, and mutated. Without the F3-Framework, AI assistants frequently introduce conflicting state patterns here.
Global State Solution
Local vs. Global State Boundaries
Server State Handling
Form State Management
Caching Strategy
Guardrail: The F3-Framework ensures Claude never introduces a competing state management pattern or violates your local vs. global boundaries.
08
DEPENDENCY BOUNDARIES
The approved vendor list — what's in, what's out, and what requires discussion before adding.
Approved Dependencies & Purpose
Banned / Avoided Packages (and why)
Policy on Adding New Dependencies
Internal Shared Libraries
Version Pinning Strategy
Guardrail: The F3-Framework ensures Claude never installs a new package without flagging it. If an approved alternative exists, it uses that instead.
09
TESTING STRATEGY
Testing patterns are highly project-specific. The F3-Framework needs this so Claude generates tests that match your approach precisely.
Testing Framework(s)
Coverage Expectations
Where Tests Live
Mocking Strategy
Test Utilities / Custom Helpers
Guardrail: Generated tests should use your testing patterns, not the framework's default examples.
10
ENVIRONMENT & DEPLOYMENT CONTEXT
How the project is built, configured, and shipped. The F3-Framework needs this for correct configuration generation.
Environment Variable Patterns
Build & Deployment Pipeline
Hosting Target
Environment-Specific Configs
CI/CD Considerations
Guardrail: The F3-Framework ensures Claude never hardcodes values that belong in environment variables and understands your deployment target.
11
"NEVER DO" LIST
The most powerful section. An explicit list of anti-patterns and hard boundaries that the F3-Framework enforces as guardrails in every session.
Type Safety Rules
Security Boundaries
Import / Path Rules
Architecture Violations
Code Style Hard Rules
Other Hard Boundaries
Guardrail: This IS the guardrail. It's your direct voice saying "these are the lines you do not cross."
Ready to Translate Your Framework?
Bring this completed worksheet to your F3-Framework session, or run the Framework Translation Prompt and let Claude guide you through it live.
Download Word Document