From tabnine
Fetches team coding guidelines for languages like TypeScript, Python, Java via tabnine-coaching tool. Use for code reviews, writing code, or standards questions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tabnine:coding-guidelinesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When the user needs to apply or check coding guidelines, use the `tabnine-coaching` MCP tool to fetch the relevant rules before responding. Do not guess or rely on training data — always fetch the actual guidelines defined for the team.
When the user needs to apply or check coding guidelines, use the tabnine-coaching MCP tool to fetch the relevant rules before responding. Do not guess or rely on training data — always fetch the actual guidelines defined for the team.
Use the get_guidelines tool from the tabnine-coaching MCP server:
language — pass the relevant programming language to filter results (e.g. TypeScript, Python, Java)skip / take — use for pagination if there are many guidelines; fetch all pages before respondingFetch guidelines first, then apply them to the code at hand. When reviewing code, explicitly reference the guideline name or description when flagging an issue.
npx claudepluginhub tabnine/skills --plugin tabnineIndexes pedantic-coder skills for universal code quality principles including naming precision, casing law, import discipline, declaration order, symmetry, and dead code intolerance. Use for code reviews, refactoring, or greenfield projects.
Provides language-agnostic guidelines for code quality, comments, error handling, and formatting when writing or reviewing code in any language. Project-specific conventions take priority.
Applies best practices from Google and industry style guides to review code for consistency, readability, and adherence using linters and formatters.