ClaudeSuperPower
SubmitLog in

output-dev-code-style

Skill

Code style conventions for Output SDK workflow projects. Use when writing or reviewing any TypeScript/JavaScript code. Discovers the project's own linting rules first; falls back to Output SDK conventions when no linter is configured.

0Developer Tools

Install

git clone https://github.com/growthxai/output.git ~/.claude/skills/output-dev-code-style

What is output-dev-code-style?

Code style conventions for Output SDK workflow projects. Use when writing or reviewing any TypeScript/JavaScript code. Discovers the project's own linting rules first; falls back to Output SDK conventions when no linter is configured.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Run shell commands

Declares Bash

~59 tokens of context used while enabled, before you invoke anything

All declared tools (4)
BashGlobGrepRead

Documentation

README · ~4 min read

Code Style Conventions

Overview

Generated code must match the style of the project it lives in. Many projects use their own linter or formatter (ESLint, Prettier, Biome, etc.) with rule sets that differ from Output's defaults. Always discover and follow the project's rules first. Only fall back to the Output SDK conventions below when the project has no linter or formatter configured.

When to Use This Skill

  • Writing any TypeScript or JavaScript code in a workflow project
  • Reviewing generated code before delivery
  • Fixing lint errors after generation

Rules Discovery (do this first)

Before writing or reviewing code, determine the project's style rules:

  1. Check for a linter config. Look for eslint.config.js, .eslintrc.*, biome.json, deno.json, or similar in the project root.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.