output
Solidoutput style linter run by the stop hook or via <path> argument
Install
Quality Score: 80/100
Skill Content
Details
- Author
- MaisonDeVolonte
- Repository
- MaisonDeVolonte/construct
- Created
- 4 weeks ago
- Last Updated
- 2 days ago
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
structured-output
Strict structured output enforcement skill. Forces Claude to produce output in exact, machine-readable formats — JSON schemas, YAML, CSV, markdown tables with defined rules, typed lists — with zero deviation, no prose contamination, no invented fields, and no schema violations. Validates output against the schema before delivery. Activates when the user needs output that will be parsed, imported, or consumed programmatically. Use when user says: output as JSON, give me YAML, strict format, no prose, just the data, machine-readable, schema-compliant, parseable output, fill this template, output only the structure, don't explain just output, match this format exactly, I'm going to parse this, structured output, follow the schema. Do NOT activate for: conversational responses, exploratory brainstorming, tasks where structured output would harm readability without adding value. First response: "Structured Output active. Paste your schema or describe the exact format you need. I'll produce and validate output befo
lint-and-style-config
Enforces a strict analysis_options.yaml built on very_good_analysis with strict-casts/strict-raw-types, a fixed set of silence-producing bug classes promoted to error (unawaited_futures, discarded_futures, empty_catches, use_build_context_synchronously, cancel_subscriptions, close_sinks, avoid_dynamic_calls, exhaustive_cases, avoid_print), dart format as the sole whitespace authority, generated-file excludes mirrored to coverage, and line-scoped-only suppression discipline; teaches the version-pinned-include trap (a missing include silently disables all rules), the errors-only-re-ranks-vs-linter-enables mechanic, and the sealed-switch analyze-vs-compile gap. Use when editing analysis_options.yaml, adding or disabling a lint, writing an `// ignore:`/`// ignore_for_file:`, bumping the Dart SDK or very_good_analysis version, wiring riverpod_lint, or explaining why discarded_futures, use_build_context_synchronously, close_sinks, or missing_provider_scope fires.
writing-user-outputs
CLI output formatting standards for worktrunk. Load before editing any code that calls warning_message, hint_message, error_message, info_message, eprintln, or println, or that produces strings the user will see (CLI help, progress UI, snapshot text). Documents ANSI color nesting rules, message patterns, and output system architecture.