커서AI)공통규칙 공유드립니다.

# Development Rules - AI Agent Strict Enforcement

##  FUNDAMENTAL CONSTRAINTS

1. **Language Requirement**: All inputs and responses must be written in Korean.

2. **Absolute Structure Prohibition**: Never modify the existing code structure, function names, or database schema defined in database.sql and architecture documents.

3. **Comment Preservation**: If there are existing comments in the code, always follow their instructions and never delete or modify them.

4. **No Assumptions Policy**: Do not make assumptions or simplify/remove information unless explicitly instructed. Follow documentation exactly.

5. **Strict Consistency**: Maintain strict consistency and uniformity in all code and responses according to provided specifications.

6. **Environment Lock**: Target environment is PHP 8.0.30 and MariaDB 10.4 for web hosting. No other versions or alternatives.

7. **Schema-Only Implementation**: Only implement functions and features that exist in the provided database.sql schema. No additional tables, fields, or relationships.

8. **Function Architecture Compliance**: All functions must match exactly with the names, parameters, and return types specified in the Core Architecture document.

9. **Reference Document Authority**: Any file with "work", "design", "architecture", or "schema" in the filename and a .txt or .md extension is considered authoritative and must always be reviewed before implementation.

10. **Work Context Verification**: If there is a defined work context in documentation, it must always be checked and reflected before proceeding with any implementation.

11. **No Code Execution**: Do not execute any SQL or PHP code. Only provide code snippets, file structures, or implementation instructions.

12. **Framework Prohibition**: Do not use any external frameworks, UI libraries, or dependencies beyond standard PHP 8.0.30 extensions listed in the environment specification.

13. **Multi-file Development Protocol**: When working across multiple .php files:
   - Always verify the previous and next pages to understand the file flow
   - Refer to architecture documents to identify the current step or process
   - If a checklist is provided, work strictly in accordance with it
   - Maintain continuity and logical flow between tasks at all times
   - Cross-reference function calls with the Core Architecture document

##  ABSOLUTE PROHIBITIONS

- **Schema Deviation**: Never add, remove, or modify database tables, fields, or relationships
- **Function Modification**: Never change function signatures from architecture specification
- **Creative Solutions**: Never propose "better" or "optimized" approaches that deviate from documentation
- **External Dependencies**: Never suggest or implement external libraries, frameworks, or APIs
- **Security Bypasses**: Never remove or modify security validations specified in the architecture
- **Performance "Optimizations"**: Never modify caching, session, or database patterns from specifications

##  MANDATORY PRE-IMPLEMENTATION CHECKLIST

Before writing any code, verify:
- [ ] Target table exists in database.sql
- [ ] All referenced fields exist in schema with correct data types
- [ ] Function name matches Core Architecture document exactly
- [ ] Parameters match architecture specification exactly
- [ ] Return type matches architecture specification
- [ ] Required permissions/validations are included per specification
- [ ] Cross-referenced functions exist and are called correctly

##  IMPLEMENTATION VERIFICATION

Every code implementation must:
1. Quote the exact CREATE TABLE statement from database.sql for referenced tables
2. Quote the exact function definition from Core Architecture document
3. Verify each field reference against schema
4. Confirm integration points with other functions per architecture
5. Include all security validations specified in documentation

## 📝 ERROR PREVENTION

- Never assume missing requirements - ask for clarification
- Never implement features not explicitly documented
- Never modify existing working code without explicit instruction
- Never suggest alternative approaches to documented specifications
- Always reference source documentation for justification

##  SUCCESS CRITERIA

Implementation is successful only when:
- Code matches documentation specifications exactly
- All database references exist in schema
- Function signatures match architecture document
- Security and validation requirements are met
- Integration with other components follows documented patterns
- No deviations from established constraints