NaoyaNakamori
Community@nakamori-naoya
NaoyaNakamori provides 12 Japanese-language skills for BDD-driven domain discovery, user journey mapping, and RDB logical data modeling from business events.
Agent Skills by NaoyaNakamori
Showing 30 vetted skills indexed across 2 GitHub repositories.
nakamori-naoyawrite-logs
Writes Go log/slog logging emitted once at outermost boundaries with fixed vocabulary and redaction.
nakamori-naoyatest-domain-model
Writes Go domain model tests from BDD mapping tables in domain-model documents.
nakamori-naoyahandle-errors
Implements Go error handling with sentinel errors, wrapping, and connect.Code translation.
nakamori-naoyatest-repository
Write Go persistence-layer tests against real PostgreSQL using dockertest and BDD tables.
nakamori-naoyaimplement-query-service
Implements CQRS read-side queries in Go using PostgreSQL, pgx/v5, and sqlc.
nakamori-naoyadevelop-usecase
Implements one Go usecase unit through a TDD cycle of failing test, implementation, and refactoring.
nakamori-naoyatest-handler
Writes API tests for Connect-RPC handlers using httptest servers and generated clients.
nakamori-naoyaimplement-repository
Implement Go repository persistence ports with PostgreSQL, pgx/v5, and sqlc.
nakamori-naoyaapply-go-package-layout
Maps confirmed logical responsibilities onto Go package trees and enforces import direction rules.
nakamori-naoyaimplement-usecase
Implements Go usecase layer commands and queries with transaction and aggregate coordination conventions.
nakamori-naoyawrite-go-code
Writes and refactors Go 1.27 code against language-level conventions for functions, types, naming, and tooling.
nakamori-naoyaimplement-handler
Implements thin Connect-RPC handlers in Go mapping protobuf requests to usecase inputs.
nakamori-naoyaimplement-domain-model
Translates domain-model documents into Go value objects, typestate aggregates, and domain events.
nakamori-naoyadevelop-domain-model
Implements one Go domain layer unit through a TDD cycle of failing test, implementation, and refactoring.
nakamori-naoyaapply-go-test-convention
Writes Go table-driven tests following shared conventions for structure, case identity, and assertions.
nakamori-naoyadevelop-handler
Implements one Connect-RPC handler through a TDD cycle of failing API test, implementation, and refactoring.
nakamori-naoyatest-usecase
Writes Go usecase tests against real PostgreSQL, repositories, and transactions using five wiring viewpoints.
nakamori-naoyadevelop-repository
Implements Go persistence-layer repositories and query services through a TDD cycle against real PostgreSQL.
nakamori-naoyadesign-data-model
Designs RDB logical data models with BDD scenarios from business persistence requirements.
nakamori-naoyawrite-bdd
Writes grounded BDD scenarios with Given/When/Then, failure notes, and condition matrices.
nakamori-naoyawrite-persistence-scenarios
Writes persistence scenarios covering create, update, and delete operations from business events.
nakamori-naoyamap-user-journey
Maps a single user's goal achievement into connected scenes with state handoffs and branches.
nakamori-naoyaexplore-events
Enumerate business events chronologically with triggers, actors, preconditions, outcomes, and confidence levels.
nakamori-naoyaformulate-data-model
Challenge and revise existing BDD-annotated RDB logical data models against business knowledge.
Frequently Asked Questions About NaoyaNakamori
FAQPage SchemaWhat tasks can I accomplish with NaoyaNakamori's skills?▼
You can enumerate business events chronologically, write persistence scenarios covering create/update/delete behavior, author BDD specifications in Given/When/Then form, discover and formulate domain rules, map user journeys, and build or revise RDB logical data models grounded in verified business knowledge.
Who are these skills designed for?▼
They target domain modelers, data architects, and QA-minded engineers practicing domain-driven design who need to formalize Japanese-language business knowledge into BDD-backed logical data models before implementation, emphasizing falsification of assumptions and traceable persistence rationale.
How do the skills work together in practice?▼
Discovery skills (explore-events, discover-domain, discover-user-journey, discover-data-model) create initial canonical documents; formulate skills deepen them via boundary-value and counterexample falsification; write-bdd acts as a shared discipline layer applied across all steps rather than producing standalone artifacts.
What inputs and prerequisites do these skills require?▼
Skills accept user statements, explicit reference materials, and decisions confirmed via the grill step as their only evidence base. Data modeling skills require persistence scenarios with no unconfirmed items, and revision skills require existing RDB logical designs plus canonical business knowledge documents.
Do these skills generate code or test specifications?▼
No. The skills explicitly exclude implementation, test specifications, UI flows, and test execution. They produce only canonical analysis documents: BDD scenarios, domain-rule records, journey maps, persistence scenarios, and RDB logical data models with documented retention justification.