You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ultimate guide to extending Claude Code with skills, agents, commands, and utilities. Covers Tresor (ready-to-use), Skill Factory (custom builds), and Skills Library (26+ domain packages).
Complete Guide to Claude Code Augmentation: Skills, Agents, Commands & Utilities (2025)
Ultimate resource for extending Claude Code with custom skills, specialized agents, slash commands, and professional utilities
Last Updated: October 28, 2025 | Author: Alireza Rezvani | License: MIT
This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.
Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.
How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Guía práctica para hacer buenas preguntas y pedir ayuda como programador
Guía integral para formular preguntas claras, reproducibles y accionables en GitHub Issues, Stack Overflow, foros y chats (Discord/Slack). Inspirada en "How do I ask a good question?" de Stack Overflow, pero ampliada para distintos canales y contextos.
Principios
Claridad primero: una buena pregunta se entiende en 30 segundos.
Reproducibilidad: cualquiera puede replicar el problema sin acceder a tu entorno.
Contexto suficiente: versiones, sistema, framework, configuración relevante.
Esfuerzo demostrado: muestras lo que intentaste y por qué no funcionó.
Respeto y foco: evita juicios, mantén el tema en una sola pregunta.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters