Setting Up Custom Rules for Your Project
By Fouad A.
14 April . 2026
Configure Syntera with project-specific rules for code style, repository structure, testing, and PR formatting to match your team's conventions.
Getting Started
Every team has conventions - naming patterns, folder structures, testing approaches, PR templates. Syntera's Custom Rules system lets you encode these so the AI follows your standards from the first line of code.
Teach Syntera your team's standards
Custom rules are persistent project configuration that shapes every plan and code generation pass. Start building
"Set it once, and every task Syntera handles follows your team's conventions automatically."
General Rules
General rules apply to all aspects of code generation. Use them for broad conventions:
Example General Rules: - Use TypeScript strict mode in all files - Prefer named exports over default exports - Use camelCase for variables, PascalCase for components - Never use console.log - use the project logger - Keep functions under 50 lines - Include JSDoc for all public APIs
These rules are injected into every agent prompt, so both the Planner and Programmer respect them.
Repository Structure
Define where files should go so Syntera generates code in the right locations:
Example Repository Structure Rules: - API routes go in src/app/api/ - Shared components go in src/components/ui/ - Page-specific components go in src/components/[page]/ - Utilities go in src/lib/ - Types go in src/types/ - Tests go in __tests__/ next to the source file
Structure rules prevent Syntera from creating files in unexpected locations or duplicating utilities that already exist.
Dependencies and Installation
Tell Syntera how your project handles dependencies:
- • Package manager preference (yarn, npm, pnpm)
- • Required setup scripts (database migrations, seed data)
- • Environment variable requirements
- • Framework-specific configuration
Example Dependency Rules: - Use Yarn as the package manager - Run 'yarn install' before any build commands - Database migrations: 'yarn prisma migrate dev' - Required env vars: DATABASE_URL, NEXTAUTH_SECRET
Testing Instructions
Specify your testing approach so Syntera generates tests that match your workflow:
- • Testing framework (Jest, Vitest, Playwright)
- • Test file naming convention
- • Coverage requirements
- • Test commands and configuration
- • Integration test patterns
Example Testing Rules: - Use Jest with ts-jest preset - Test files: *.test.ts next to source - Integration tests: *.int.test.ts in __tests__/ - Minimum 80% coverage on new code - Run tests: 'yarn test'
Pull Request Formatting
Control how Syntera formats the pull requests it creates:
- • PR title format (conventional commits, ticket numbers)
- • Description template sections
- • Required labels or reviewers
- • Commit message conventions
- • Change summary format
Conclusion
Custom rules are a one-time investment that pays off on every task. Once configured, Syntera generates code that feels like it was written by someone who already knows your codebase inside and out.
Related Guides
Writing Better Task Descriptions
Learn how to write clear, effective task descriptions that help Syntera's AI produce better plans and cleaner code on the first try.
CEO/Portfolio Confirmation
A modular portfolio landing page with dynamic sections, SEO controls, and reusable hero layouts ready to personalize.
How BRD and SRS Documents Power Your Plans
Understand how Syntera generates Business Requirements Documents and System Requirements Specifications to ensure every project starts with clear, structured intent.