Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.

I understand these skills can contain unsafe or unintended behavior, and I will review and security-scan before use. No warranty, suitability, or outcome is guaranteed.

Developer ExperienceFree Safe

Tooling Engineer

Security Scan Summary

Status: Safe

Source: Syntic Skills registry

Automated security scan completed with no high-risk patterns detected. Manual review is still required.

About This Skill

Use when configuring linters, formatters, type checkers, and writing custom static analysis rules

Downloadable SKILL.md

Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.

SKILL.md

---
name: Tooling Engineer
description: Use when configuring linters, formatters, type checkers, and writing custom static analysis rules
category: Developer Experience
version: 1.0.0
tools: []
---

# Tooling Engineer

Configure and extend static analysis tools enforcing codebase consistency: ESLint, Prettier, Biome, Ruff, clippy, golangci-lint. Write custom lint rules for domain patterns and build code generation tools.

## Audit & Configure

1. Audit existing tooling for conflicts, redundant rules, gaps by examining configs, pre-commit hooks, CI static analysis steps
2. Resolve formatter/linter conflicts: formatters own whitespace/syntax, linters own code patterns/correctness
3. Categorize linter rules by severity: errors block commits (correctness), warnings should be addressed (style preferences)
4. Write custom lint rules for project patterns: import conventions, preventing direct DB access outside data layer, requiring error boundaries
5. Configure formatter for all file types: markdown, JSON, YAML, CSS, source code
6. Configure type checker with strict mode: strict null checks, no implicit any, exhaustive switch statements
7. Build code generation tools using AST libraries (ts-morph, syn, jscodeshift) for repetitive patterns: route registration, dependency injection, API client generation
8. Create shared configuration package for org-wide reuse, versioned independently with clear migration guides
9. Integrate into dev lifecycle: editor extensions for real-time feedback, pre-commit hooks for validation, CI enforcement
10. Document rationale for each non-default rule so teams understand the "why" and propose changes through governance

## Standards

- Single canonical config file per tool, not spread across multiple formats
- Custom rules include test cases covering positive (should trigger) and negative (should pass) examples
- Auto-fixable rules produce correct output without intervention; non-fixable rules provide clear instructions
- Formatter output deterministic: running twice produces identical output
- Profile tool execution; disproportionately slow rules optimized or moved to CI-only
- Generated code includes header comment indicating generated status

Bundle Download

Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.

Install Targets

Syntic App

1. Create a dedicated folder for this skill in your local skills library.
2. Place SKILL.md into that folder.
3. Restart Syntic and invoke this skill on matching tasks.

Syntic Code (CLI)

1. Save SKILL.md in your local Syntic Code skills directory.
2. Keep related files in the same skill folder.
3. Run in a safe environment and validate outputs.

Source

https://github.com/rohitg00/awesome-claude-code-toolkit/blob/main/agents/developer-experience/tooling-engineer.md

Open Source Link

Developer Experience

Related Skills