All authors
Claude Skills by makifbaysal
github.com/makifbaysal115 skills1 installs122 views
- Analiz Task WorkflowProcedure for an analiz (analysis) task when you hold the analyst role. Use when a task with task_type analiz is assigned to you and add_task_document is in your tool list.Votes: 0GitHub stars: 109
- Api Contract OpenapiUse when you add or change any HTTP endpoint's request or response shape (Go or Java) — implement the task's contract exactly, evolve additively, keep the OpenAPI document in sync, and detect breaking changes before hand-offVotes: 0GitHub stars: 109
- Cloud Deploy Gcp AwsUse when a backend or worker service needs a cloud deploy - container-first GitHub Actions deploys to Google Cloud Run (WIF) or AWS ECS/App Runner (OIDC), with migrate-before-deploy and a health-check gateVotes: 0GitHub stars: 109
- Fiber Rest ApiUse when adding or changing a Go HTTP endpoint — Fiber v2 or v3 (detect which), thin handlers, central error mapping, boundary validation; the same rules apply to net/http, chi, echo or ginVotes: 0GitHub stars: 109
- Go Hexagonal ArchitectureUse when adding a use case, port, repository or adapter in a Go service — where each piece goes, how errors and transactions cross layers, and how to check the import directionVotes: 0GitHub stars: 109
- Java Oop Solid DesignUse when modelling a rich domain in Java - SOLID principles, encapsulated entities that enforce their own invariants, and value objects over primitivesVotes: 0GitHub stars: 109
- Java PersistenceUse when a Java service reads or writes the database - JPA/Hibernate and Panache/Spring Data mapping, transaction boundaries, pagination and avoiding N+1 and entity-over-the-wire leaksVotes: 0GitHub stars: 109
- Java Testing Junit MockitoUse when writing tests for Java (Quarkus or Spring) code - JUnit Jupiter structure, Mockito for collaborators, test slices, Testcontainers, and framework-native integration tests, test-firstVotes: 0GitHub stars: 109
- Java Vs Go DecisionUse when starting a backend task that could be built in either language - decide Go vs Java (Quarkus/Spring) from the task's shape and the repository's existing stackVotes: 0GitHub stars: 109
- Mockery Suite TestsUse when writing Go tests that need test doubles or cover multiple cases - detect the repo's mocking approach (Mockery v3, gomock, hand-written testify mocks, fakes), table-driven cases, testify suites when the repo uses them, and real-Postgres tests for repository adaptersVotes: 0GitHub stars: 109
- Postgres MigrationsUse when changing the database schema - detect the repo's migration tool, ship a new migration in its layout, never edit an applied one, and avoid lock-unsafe DDL on a live tableVotes: 0GitHub stars: 109
- Quarkus Service ArchitectureUse when building or extending a Java service with Quarkus - layered architecture, JAX-RS resources, CDI beans, Panache persistence, and native-friendly patternsVotes: 0GitHub stars: 109
- Spring Boot FallbackUse when Java is chosen but Quarkus does not fit - build the service with Spring Boot using the same clean layering, only when a required library lacks a Quarkus extension or the repo already standardizes on SpringVotes: 0GitHub stars: 109
- Zerolog ObservabilityUse when adding logging to Go code - the repository's logger with structured fields, request-scoped correlation, correct levels, no secrets or double-loggingVotes: 0GitHub stars: 109
- Accessibility BasicsUse on every UI change - semantic HTML, labels for controls, keyboard-navigable dialogs/menus, visible focus, and never color as the only signalVotes: 0GitHub stars: 109
- Api Client IntegrationUse when a component talks to the backend - go through the typed api client, type every response, and handle loading, success, and error states explicitlyVotes: 0GitHub stars: 109
- Cloud Deploy Gcp AwsUse when a web/frontend app needs a cloud deploy - GitHub Actions to Cloud Run/ECS for SSR or GCS+CDN/Firebase and S3+CloudFront for static, with build-time env and cache invalidationVotes: 0GitHub stars: 109
- Component CompositionUse on every UI change - Atomic Design levels, reuse-before-build, correct placement, and import direction through the shared component library.Votes: 0GitHub stars: 109
- Component TestingUse when writing or changing any React component - React Testing Library tests are behavior-focused (byRole first), use user-event, assert on accessible output, one behavior per test, and run in npm testVotes: 0GitHub stars: 109
- React Typescript PatternsUse when writing React + TypeScript components - functional components, explicit typed props, derived state over effects, and no any/unsafe castsVotes: 0GitHub stars: 109
- Routing StateUse when adding routes or deciding where state lives - carry resource ids and navigation-surviving state in the URL, keep route components thin, and lift shared state to a hook not a global storeVotes: 0GitHub stars: 109
- Vite Tailwind RadixUse when styling any web UI - style with Tailwind utility classes and design tokens, avoid custom CSS, and build on the existing Radix/shadcn primitives instead of hand-rollingVotes: 0GitHub stars: 109
- Android Compose PatternsUse when building native Android with Jetpack Compose - stateless composables, state hoisting, ViewModel-owned state, edge-to-edge, predictive back, adaptive layout, atomic components, and Material theming over hardcoded valuesVotes: 0GitHub stars: 109
- App Store DeployUse when a mobile app needs a release pipeline - fastlane GitHub Actions to TestFlight (iOS) and Play internal track (Android), with code signing and the release naming that maps to TaskTrooper's prod deployVotes: 0GitHub stars: 109
- Flutter Atomic ComponentsUse when adding or reusing Flutter UI - organize widgets as atoms, molecules, and organisms in a shared library and never hand-roll a component that already existsVotes: 0GitHub stars: 109
- Flutter State ManagementUse when a Flutter screen needs app state or data - separate presentation from state, keep business logic out of widgets, and follow the app's existing state solution (Riverpod 3 Notifier/AsyncNotifier, or the official ChangeNotifier+ListenableBuilder MVVM pattern)Votes: 0GitHub stars: 109
- Flutter TestingUse when testing Flutter code - unit tests for logic, widget tests for UI behavior, golden tests for appearance, the multi-size/text-scale/dark matrix, accessibility guidelines, test-firstVotes: 0GitHub stars: 109
- Flutter Widget ArchitectureUse when building Flutter screens - compose small stateless widgets, keep layout declarative, decide layout by available width not device/orientation, separate presentation from business logic, and use the theme not hardcoded stylesVotes: 0GitHub stars: 109
- Mobile NavigationUse when adding a screen, a tab, a deep link, or back-navigation handling - the per-stack navigation APIs, state preservation, auth-boundary resets, and how to verify a deep link actually opens the right screen.Votes: 0GitHub stars: 109
- Mobile Ui UxUse when designing or building any mobile screen or component a user sees (Flutter, SwiftUI or Compose) - platform conventions, hierarchy, type that scales, colour roles and dark mode, safe areas and insets, forms and keyboard, states, feedback, and the generic-mobile anti-patterns.Votes: 0GitHub stars: 109
- Native Vs Flutter DecisionUse when starting a mobile task that could be Flutter or native - decide from the existing app, platform-specific needs, and the analiz taskVotes: 0GitHub stars: 109
- Offline SyncUse when a screen must work without network or a mutation must survive a lost connection - local storage choice, the outbox pattern with idempotency keys, background replay, and how to test it with a fake clock and fake network.Votes: 0GitHub stars: 109
- Platform PermissionsUse when a feature needs camera, location, photos, notifications, contacts, microphone, Bluetooth, or local network - the per-platform request flow, every denial state, and how to actually test the denied path when the shared test device auto-grants permissions.Votes: 0GitHub stars: 109
- Swiftui PatternsUse when building native iOS with SwiftUI - small composable views, observable state models, atomic components, Swift 6.2+ concurrency, and system styling over hardcoded valuesVotes: 0GitHub stars: 109
- Acceptance Criteria GwtUse when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative casesVotes: 0GitHub stars: 109
- Analiz GateUse when deciding whether a request needs an analiz task before implementation - the conditions that require the architect's analysis versus going straight to implementationVotes: 0GitHub stars: 109
- Analiz Task SpecUse when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand overVotes: 0GitHub stars: 109
- Answer Workspace QuestionsUse when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approvalVotes: 0GitHub stars: 109
- Backlog PrioritizationUse when ordering board tasks - set priority/blocked_by/deploy_depends_on by severity and dependency, split MoSCoW within a feature, and use RICE/ICE only for a genuine "what next" call across several featuresVotes: 0GitHub stars: 109
- Board Column FlowUse when moving tasks or reporting status - the kanban column semantics, which columns are human/architect/QA gates, and where the PM actually actsVotes: 0GitHub stars: 109
- Implementation Task SpecUse when you create an implementation board task directly - the required fields, one-role-one-deliverable rule, and dependency orderingVotes: 0GitHub stars: 109
- Pm As Solo OrchestratorUse when planning a delivery request as the only orchestration agent - one board-writing subtask, backlog first, one approval question, then move approved tasks to todoVotes: 0GitHub stars: 109
- Pm Uat ReviewUse when a task is in pm_uat - verify every acceptance criterion and the human's comments yourself in the browser, on a device, or over a loopback HTTP request, record a verdict per criterion, then move to human_uat or need_revisionVotes: 0GitHub stars: 109
- Post Analiz HandoffUse when the stakeholder asks about an analysis outcome or its implementation tasks - understand the human approval gate and review the tasks the architect created once the human approvedVotes: 0GitHub stars: 109
- Project Repo ManagementUse when organizing the workspace - create/rename initiative projects and link repositories to them directly, since these are factual actions needing no analiz or approvalVotes: 0GitHub stars: 109
- Release Notes WritingUse when the stakeholder asks for release notes or a changelog - group done/released work into Added, Changed, Deprecated, Removed, Fixed and Security, in outcome language, with task referencesVotes: 0GitHub stars: 109
- Requirements DocumentUse when a product decision or feature needs a written record - what to capture in a task document (PRD, decision record) and where to attach it, since TaskTrooper has no epicVotes: 0GitHub stars: 109
- Requirements WritingUse when capturing what a feature must do - write testable user-story requirements that state WHAT and WHY, never HOW, with assumptions made explicitVotes: 0GitHub stars: 109
- Scope ManagementUse when defining a feature - name what is in scope, out of scope, and assumed, and handle mid-flight expansion without corrupting in-progress tasksVotes: 0GitHub stars: 109
- Stakeholder CommunicationUse when updating the stakeholder - report in outcome language (what changed for users, what's next, what decision is needed), translate technical detail, and surface risks earlyVotes: 0GitHub stars: 109