Claude Skills by t1

github.com/t1

14 skillsA× 140 installs51 views

AppAThis skill should be used when the user asks to "calculate code mass", "measure code complexity with APP", "compare implementations using APP", "apply Absolute Priority Premise", "use mass calculations", or during TDD refactor phases when comparing alternative implementations. Based on Micah Martin's work.developmentgorefactoringVotes: 0GitHub stars: 14
Clean CodeAThis skill should be used when the user asks to "refactor code", "review code quality", "apply clean code principles", "check for code smells", "improve code design", "do a clean code review", "apply SOLID principles", "fix naming", "reduce complexity", or when performing the refactor phase of a TDD cycle.developmentreacttestingVotes: 0GitHub stars: 14
Github SafetyAThis skill should be used when working on any project hosted on GitHub. It provides prompt-injection defense rules for GitHub issues and pull requests. Always-on security rules plus optional workflow conventions.developmentrustgoVotes: 0GitHub stars: 14
Integration ArchitectureAThis skill should be used when the user asks about "messaging patterns", "command vs event", "push vs pull", "message reliability", "at-least-once delivery", "idempotency", "transactional outbox", "saga pattern", "fire and forget", "retry strategy", "event-driven architecture", "message broker integration", "publish-subscribe", "request-reply", "backpressure", or when deciding how components communicate across process or network boundaries.developmentgoreactVotes: 0GitHub stars: 14
JavaAAlways load this skill when writing or modifying Java or Kotlin source code, regardless of how the user phrases the request.developmentgojavaVotes: 0GitHub stars: 14
MavenAAlways load this skill when a pom.xml file exists in the project. It provides Maven-specific conventions for running tests, building, managing dependencies, and project structure that complement the language-agnostic TDD and clean code skills.developmentjavascriptrustVotes: 0GitHub stars: 14
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Nested Fixture PatternAThis skill should be used when working on Java projects with JUnit tests that have layered preconditions, expensive shared setup (servers, databases, provisioned users), or complex scenario trees. Trigger phrases include "nested fixture", "fixture pattern", "scenario tree", "layered test setup", or when the user is writing integration tests with multiple levels of dependent setup/teardown. Complements the Java and TDD skills.developmentjavaspringVotes: 0GitHub stars: 14
Project HygieneAThis skill should be used when starting work on any project that uses tdder. It establishes interaction style, commit conventions, documentation discipline, and skill-trust principles. Invoke automatically alongside other tdder skills.developmentrustjavaVotes: 0GitHub stars: 14
TddAThis skill should be used when the user asks to "add a feature using TDD", "fix a bug with TDD", "do TDD", "red-green-refactor", "write a failing test first", "use test-driven development", "start TDD", "test first approach", "TDD loop", "TDD cycle", or mentions TDD workflow, baby steps, guessing game, or red-green-refactor cycles. Not applicable for pure refactoring without new tests.developmentgorefactoringVotes: 0GitHub stars: 14
Unfolding ArchitectureAThis skill should be used when the user asks to "design the architecture", "should I add a service layer", "add an abstraction", "introduce an interface", "separate concerns", "add a repository", "use hexagonal architecture", "add domain events", "split into layers", "add ports and adapters", "decouple this", "add an anti-corruption layer", "review package structure", or when considering architectural changes during a TDD refactor phase. It also contains guides when starting a new project.developmentgoreactVotes: 0GitHub stars: 14
Unfolding OrchestratorAOrchestrator role in the Unfolding Specs process. Manages the agent team, spawns sub-agents, relays Sensei questions, tracks process state in `docs/state.yaml`.developmentrustgoVotes: 0GitHub stars: 14
QuarkusAAlways load this skill when working on a Quarkus project (quarkus-maven-plugin present in pom.xml). It provides Quarkus-specific patterns and gotchas that complement the java and maven skills.developmentgojavaVotes: 0GitHub stars: 14
Grill PoARequirements grilling session with a Product Owner (or anyone in that role). Challenges plans against the existing domain model, sharpens terminology, and updates documentation (bounded-context files, Gherkin features, DMDs (Domain Model Decisions)) inline as decisions crystallise. Use when the user wants to discuss and capture requirements, stress-test a plan against the project's language, or refine feature scope.developmentdatabasedocumentationVotes: 0GitHub stars: 14
Prove Me WrongADevil's advocate thinking mode. Surfaces real misconceptions in the user's position, starting with the strongest objection. Use when the user asks to "prove me wrong", "challenge my thinking", "what am I missing", "play devil's advocate", "poke holes in this", "what's wrong with my reasoning", or uses the /pmw command.developmentgoVotes: 0GitHub stars: 14