shalin-rahman/skills/code-quality-linting
skills/code-quality-linting/SKILL.md
# Playbook: Zero-Defect Code Quality (Principal Engineer Grade) This playbook defines the mandatory quality standards for all code generated by the Synaptic Framework. Follow these rules to ensure production-grade stability and pass all automated linters (Pylint, Flake8, MyPy). ## 1. Zero-Trust Linting - **PEP8 Compliance**: All Python code must strictly follow PEP8. This includes: - Exactly 4 spaces for indentation. - Max line length of 88 characters (Black style). - Clear separat
$ install --global
skillsauthnpx skillsauth add shalin-rahman/Synapticity skills/code-quality-lintingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 12:43 AM224.9s1 file scanned
SKILL.md
Playbook: Zero-Defect Code Quality (Principal Engineer Grade)
This playbook defines the mandatory quality standards for all code generated by the Synaptic Framework. Follow these rules to ensure production-grade stability and pass all automated linters (Pylint, Flake8, MyPy).
1. Zero-Trust Linting
- PEP8 Compliance: All Python code must strictly follow PEP8. This includes:
- Exactly 4 spaces for indentation.
- Max line length of 88 characters (Black style).
- Clear separation of imports (Standard Lib, Third-Party, Local).
- No Unused Variables: Never declare a variable or import that isn't used.
- Explicit Returns: Every function must have an explicit return path, including
Noneif applicable.
2. Robust Type Safety
- Type Hinting: All function signatures MUST include type hints for every argument and the return value.
- Pydantic v2: If handling data models, use Pydantic v2
BaseModelfor validation. - Checkable Code: Ensure code passes
mypy --strictwhenever possible.
3. Defensive Programming
- Error Handling: Encapsulate external I/O or network calls in specific
try...exceptblocks with precise exception types. Never use a bareexcept:. - Validation: Validate all inputs at the entry point of a function.
- Graceful Failure: Always provide a fallback or sensible error message if a core component fails.
4. Documentation & Docstrings
- Google Style: Use the Google Python Style Guide for all docstrings.
- The "Why", not the "What": Comments should explain the rationale behind non-obvious logic, not just restate the code.
5. Architectural Idioms
- SOLID Principles: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion.
- Factory Patterns: Use factories or adapters when dealing with multiple providers.
- Async Efficiency: Use
asynciofor I/O bound operations to maximize throughput.
Applying this skill ensures that every line of code produced is ready for an enterprise-grade CI/CD pipeline.
Related Skills
shalin-rahman/skills/zero-defect-engineering
tools
VerifiedTrustedCommunity
# Skill: Zero-Defect Software Engineering # Focus: Writing immortal, self-documenting, and resilient source code. ## Playbook Strategy: 1. **SOLID Foundations**: - **Single Responsibility**: Every class/function does ONE thing perfectly. - **Open/Closed**: Design for extension without modification. 2. **DRY (Don't Repeat Yourself)**: If logic appears twice, abstract it into a utility or base class. 3. **Defensive Programming**: - Validate every input. - Handle every exception specif
1SKILL.mdUpdated Apr 22, 2026
shalin-rahman/skills/typescript-clean
development
VerifiedTrustedCommunity
# Skill: TypeScript Clean Code (Staff Engineer) # Usage: Use for any TypeScript-based project to ensure enterprise-grade type safety and readability. ## Core Rules: - **Strict Typing:** Never use `any`. Use `unknown` with type guards if the type is truly uncertain. - **Interfaces vs Types:** Use `interface` for public APIs (extendability) and `type` for unions, intersections, and primitives. - **Functional Patterns:** Prioritize immutability. Use `readonly` for arrays and objects where possible
1SKILL.mdUpdated Apr 22, 2026
shalin-rahman/skills/testing-strategies
development
VerifiedTrustedCommunity
# Skill: Advanced Testing Strategies (TDD / BDD) # Usage: Use to enforce high code quality, prevent regressions, and ensure requirements are met implicitly. ## 🧪 The Testing Pyramid - **Unit Tests (70%)**: Fast, isolated tests for individual functions and classes. Mock all external dependencies. - **Integration Tests (20%)**: Test the interaction between several units or external systems (e.g., Database, APIs). - **End-to-End (E2E) Tests (10%)**: Slow, brittle tests that verify the system as a
1SKILL.mdUpdated Apr 22, 2026
shalin-rahman/skills/technical-writing-standards
development
VerifiedTrustedCommunity
# Skill: Technical Hand-off & Clarity # Focus: Professional documentation for human and machine consumption. ## Playbook Strategy: 1. **The "ReadMe First" Rule**: Use structured, hierarchical markdown. High-level summary first, deep-dive implementation second. 2. **Contextual Grounding**: Explain the "Why" and the "How" for every project. 3. **Semantic Clarity**: Use industry-standard terminology. Avoid jargon where simple language suffices. 4. **Machine-Readable Annotations**: Include clear co
1SKILL.mdUpdated Apr 22, 2026