developer-tooling

Configure linting, formatting, bundling, and code generation for developer tooling.

16|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill developer-tooling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-tooling
Source: https://github.com/JCETools-Petra/JCE-Opencode-Tools/tree/main/config/skills/developer-tooling
Command: npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill developer-tooling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you set up and maintain a consistent developer toolchain so code quality, formatting, and project structure stay reliable across the lifetime of a repository.

Core Features & Use Cases

  • LSP-first developer setup: Choose and align editor tooling for navigation, diagnostics, and safer refactors.
  • Linting + formatting decisions: Pick the right formatter/linter combo (Biome, ESLint+Prettier, Ruff, rustfmt/clippy, gofmt+golangci-lint) and avoid configuration conflicts.
  • Bundler and runtime guidance: Select appropriate build tooling (tsup, unbuild, bun build, Vite 6) and ensure the dev/build workflow matches your app type.
  • Code generation workflows: Integrate OpenAPI/Prisma/GraphQL codegen with clear rules so generated code stays correct and doesn’t get hand-edited.
  • Project structure & verification: Establish a scalable feature-based layout and a checklist-driven CI gate to prevent regressions.

Quick Start

Start by configuring Biome for linting and formatting to enforce consistent style and import organization in the repository.

Frequently Asked Questions about developer-tooling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate ESLint and Prettier to Biome for linting and formatting?

Migrating ESLint and Prettier to Biome involves replacing their configurations with a single Biome config to enforce consistent style and import organization without conflicts. This Skill provides concrete configuration templates and decision trees to execute the migration.

What's the best way to configure Vite builds for a TypeScript web project?

Configuring Vite builds for a TypeScript project requires selecting appropriate build tooling that matches your app type and dev workflow. This Skill provides guidance on aligning Vite 6 configurations alongside other bundlers like tsup or unbuild.

How do I set up OpenAPI, Prisma, or GraphQL codegen workflows?

Setting up OpenAPI, Prisma, or GraphQL codegen requires integrating generation tools with clear rules ensuring generated code stays correct and avoids manual editing. This Skill supplies actionable workflows to automate code generation safely.

Does this developer tooling guidance support Python, Rust, and Go linters?

Yes, the linting and formatting guidance supports Ruff for Python, rustfmt and clippy for Rust, and gofmt with golangci-lint for Go. It helps you pick the right formatter and linter combo to avoid configuration conflicts across these environments.

How do I enforce consistent code formatting and linting in CI pipelines?

Enforcing consistent code formatting and linting in CI requires establishing a checklist-driven CI gate to prevent regressions and manual drift. This Skill helps configure verification checklists ensuring toolchain consistency throughout the repository lifetime.

Why do I need an LSP-first developer setup for my project?

An LSP-first developer setup aligns editor tooling for navigation, diagnostics, and safer refactors across your codebase. This Skill standardizes the selection and configuration of LSP-related workflows to maintain reliable project structure and code quality.