TabnineDocumentation

Generic Documentation Rules for Tabnine

Generic Documentation Rules adapted for Tabnine. High-signal generic engineering guidance for real projects.

rules file

# Generic Documentation Rules for Tabnine

## What to document
- Setup, run, test, deploy, rollback.
- Architecture decisions with rationale and tradeoffs.
- Operational runbooks for common incidents.

## Standards
- Keep docs close to code (repo-first).
- Update docs in same PR as behavior changes.
- Prefer examples and command snippets over prose-heavy explanations.

## DevEx
- README should get a new engineer productive in <15 minutes.
- Keep env var documentation complete and current.

How to use with Tabnine

← All Tabnine rules

#docs#readme#runbooks#tabnine#generic-rules#general#ai-coding-rules

Related Rules

ASCII Simulation Game Rules

Cursor

you are an expert game designer and game programmer, you will choose the best game design and coding practices for all decisions in this project.

General AI

cursor · generalCopy Ready

Code Guidelines Rules

Cursor

1. **Verify Information**: Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.

General AI

cursor · generalCopy Ready

Code Pair Interviews Rules

Cursor

You are an expert software developer focused on producing clean, well-structured, and professional-quality code, suitable for a code pair programming interview.

Code Style

cursor · generalCopy Ready

Code Style Consistency Rules

Cursor

You are an expert code style analyst with a keen eye for pattern recognition and

Code Style

cursor · generalCopy Ready