architecture-best-practices

Detect tech stacks from package.json and generate docs/best-practices.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yuch4/dx-selecta --skill architecture-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-best-practices
Source: https://github.com/yuch4/dx-selecta/tree/main/.claude/skills/architecture-best-practices
Command: npx skills add https://github.com/yuch4/dx-selecta --skill architecture-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill analyzes a project's tech stack and documents architecture best-practice guidelines.

Core Features & Use Cases

  • Detects the project tech stack from package.json and configuration files and generates a stack-specific best-practices document.
  • Produces actionable patterns, anti-patterns, and deployment considerations to support onboarding and consistent coding standards.
  • Uses references to tailor guidance for common stacks (e.g., Next.js App Router, Supabase) and outputs to docs/best-practices.md.

Quick Start

Run the architecture-best-practices skill on a repository to generate docs/best-practices.md.

Frequently Asked Questions about architecture-best-practices

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

FAQPage Schema
How do I generate architecture best-practice documentation for my project?

You can generate architecture best-practices documentation by running a skill that detects your tech stack from package.json and config files, then outputs actionable guidelines to docs/best-practices.md.

What tech stacks are supported for generating architecture best-practice docs?

The skill detects stacks from package.json and configuration files, providing tailored guidance for common stacks like Next.js App Router and Supabase.

How does stack detection from package.json work for documentation generation?

Stack detection reads package.json and configuration files to identify frameworks and libraries, enabling the generation of stack-specific architecture guidelines.

Can I use this approach to create onboarding guides with coding standards?

Yes, it produces actionable patterns, anti-patterns, and deployment considerations designed to support onboarding and maintain consistent coding standards.

What is the best way to document anti-patterns and code patterns for a new repository?

Automate the process by analyzing repository configuration files to generate a stack-specific markdown file containing code patterns and anti-patterns for development reference.