ai-development-guide

Apply technical decision criteria and anti-pattern detection to software quality workflows.

666|102|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/shinpr/claude-code-workflows --skill ai-development-guide-shinpr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-development-guide
Source: https://github.com/shinpr/claude-code-workflows/tree/main/skills/ai-development-guide
Command: npx skills add https://github.com/shinpr/claude-code-workflows --skill ai-development-guide-shinpr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps engineering teams standardize decision criteria, detect anti-patterns, and implement debugging and quality assurance workflows, reducing risk and accelerating delivery.

Core Features & Use Cases

  • Technical anti-pattern catalog and fail-fast principles to guide design and coding decisions.
  • Structured decision documentation and ADR guidance to capture rationale and approvals.
  • Comprehensive debugging techniques, error analysis, and root-cause methods for faster remediation.
  • Quality check workflows applicable across languages to ensure consistent governance and release readiness.

Quick Start

Review the documented patterns and apply the Fail-Fast guidelines to your current project tasks.

Frequently Asked Questions about ai-development-guide

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

FAQPage Schema
How do I detect software anti-patterns during design reviews?

Detect software anti-patterns during design reviews by applying fail-fast principles and a structured anti-pattern catalog to guide coding decisions and prevent common design faults before implementation.

What is the best way to document technical decisions for engineering teams?

Document technical decisions using structured decision documentation and Architecture Decision Records (ADR) guidance to capture rationale and approvals, ensuring explicit error handling requirements and clear decision records are met.

How do I apply root-cause analysis methods for faster debugging remediation?

Apply root-cause analysis methods for faster debugging remediation by utilizing comprehensive debugging techniques and error analysis workflows to identify underlying issues and constrain risk during quality assurance.

Does this quality assurance workflow support multiple programming languages?

Yes, the quality check workflows are applicable across languages to ensure consistent governance and release readiness, providing language-agnostic quality assurance and structured testing practices for your engineering teams.

When do I need structured risk analysis for software quality?

You need structured risk analysis for software quality when applying robust technical decision criteria across debugging sessions and design reviews to prevent common design faults, constrain risk, and satisfy explicit error handling requirements.