skills/loqui/SKILL.md
Access language-specific coding guidelines from loqui. Use when implementing code and needing patterns, style guidance, or best practices for Python, Go, Rust, or Bash.
npx skillsauth add srnnkls/tropos loquiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Language guidelines for writing code with eloquence and style.
Loqui resources are in this skill's directory:
~/.claude/skills/loqui/reference/loqui/languages/{language}/
Use Read tool (not Glob) to access - paths outside cwd require direct reads.
| Language | Path |
|----------|------|
| Python | ~/.claude/skills/loqui/loqui/languages/python/ |
| Go | ~/.claude/skills/loqui/loqui/languages/go/ |
| Rust | ~/.claude/skills/loqui/loqui/languages/rust/ |
| Bash | ~/.claude/skills/loqui/loqui/languages/bash/ |
Each language directory follows this structure:
{language}/
├── README.md # Overview, core principles, anti-patterns checklist
├── quality.md # Naming, comments, documentation conventions
├── composition.md # Structuring behavior (classes/functions/modules)
├── modules.md # Package structure, organization, public APIs
├── errors.md # Error handling patterns
└── ... # Additional language-specific resources
Start with the README for quick reference and core principles.
~/.claude/skills/loqui/reference/loqui/languages/{language}/README.mdShared across all languages:
implement - Generic implementation methodologytest - TDD workflowcode - Code domain (references loqui for compliance review)tools
External code-review harness (`peer` zsh tool): canonical model registry, idle-stall watchdog, and self-parallelising fan-out to codex/gemini. Use when dispatching external (non-Claude) reviewers from the review or implement pipelines — call `peer run`/`peer <harness>` instead of `codex exec`/`gcloud`+Vertex directly.
testing
Unified validation dispatcher. Auto-detects validation type from argument or presents selection menu. Routes to test, implement (verify), or hooks-test.
development
Test-driven development methodology (RED-GREEN-REFACTOR). Use when implementing features, fixing bugs, or changing behavior - write failing test first, then minimal code to pass.
development
Create new Claude Code skills following project patterns and best practices. Use when building new skills, extracting reusable capabilities, or converting commands to skills.