All authors

Claude Skills by yutna
github.com/yutna43 skills0 installs0 views
- Functional Applying Solid FunctionallyUse when a function takes a whole service to use one part, when adding a variant forces edits everywhere, or when structuring module dependencies.Votes: 0GitHub stars: 2
- Functional Capturing The DomainUse when starting a feature or system, when code and the business use different words for the same thing, or when drawing boundaries between subsystems.Votes: 0GitHub stars: 2
- Functional Choosing Precise NamesUse when naming a function, type or variable, when a name is vague like data or handle, or when a name is generic or unusually hard to pick.Votes: 0GitHub stars: 2
- Functional Choosing Types Or Plain DataUse when a shape could be a type or a generic map, when fields or columns vary by tenant or user, when a schema must be a value, or when wrapper types block generic code.Votes: 0GitHub stars: 2
- Functional Composing FunctionsUse when two steps do not fit together, when deciding parameter order, or when a signature is partial rather than total.Votes: 0GitHub stars: 2
- Functional Constraining Primitive ValuesUse when domain values are raw strings or numbers, when the same format or range check appears in more than one place, or when ids can be swapped.Votes: 0GitHub stars: 2
- Functional Crossing Io BoundariesUse when mapping domain types to JSON, database rows or payloads, when storage shape leaks into the model, or when a read-only screen rebuilds aggregates and a bad row blanks it.Votes: 0GitHub stars: 2
- Functional Deciding What MattersUse when code is correct but hard to follow, when deciding what an interface should expose, or when a reader cannot tell which parts are important.Votes: 0GitHub stars: 2
- Functional Defining Errors Out Of ExistenceUse when error handling dwarfs the happy path, when the same failure is handled in many places, or when an interface forces callers to handle rare cases.Votes: 0GitHub stars: 2
- Functional DesignUse when starting design or review, deciding how much design a task warrants, from a throwaway script to a subsystem, unsure which skill fits, or the requirement is undecided.Votes: 0GitHub stars: 2
- Functional Designing Deep ModulesUse when designing a module interface, when it exports nearly as much as it hides or is as complicated as its implementation, or when tiny one-function modules multiply.Votes: 0GitHub stars: 2
- Functional Designing What To ObserveUse when deciding what to log, trace, or measure, when an incident could not be diagnosed from what was recorded, or when adding observability late.Votes: 0GitHub stars: 2
- Functional Designing Workflow PipelinesUse when implementing a use case, command handler, or business process, or when logic for one operation is scattered across services and layers.Votes: 0GitHub stars: 2
- Functional Diagnosing ComplexityUse when a small change touches many files, an edit breaks an unexpected module, code is slow to read, or before refactoring a flag, cache or field that may be self-inflicted.Votes: 0GitHub stars: 2
- Functional Elixir PhoenixUse when designing a Phoenix context, an Ecto schema or changeset, a LiveView's assigns, or deciding what belongs in the domain rather than in the web layer.Votes: 0GitHub stars: 2
- Functional ElixirUse when designing Elixir structs, ok and error tuples, or `with` pipelines, and whether a GenServer, a supervision tree, or letting a process crash is the right answer.Votes: 0GitHub stars: 2
- Functional Enforcing Consistency BoundariesUse when deciding what one transaction must cover, when two entities have to stay in step, or when identity and equality of domain values are unclear.Votes: 0GitHub stars: 2
- Functional Folding Over DataUse when a loop accumulates into a variable, when combining a collection into one value, when the same tree walk keeps being written again, or when a combining law matters.Votes: 0GitHub stars: 2
- Functional Handling Errors With ResultsUse when a function throws and callers cannot tell, when exceptions cross module boundaries, or when validation must report every problem.Votes: 0GitHub stars: 2
- Functional Hiding InformationUse when callers know how a module works inside, when one data format appears in several modules, or when each step of a process became a module.Votes: 0GitHub stars: 2
- Functional JavascriptUse when applying functional design in plain JavaScript, without a type checker, including immutability, tagged unions, and Result-style error handling.Votes: 0GitHub stars: 2
- Functional Making Effects ReliableUse when a timeout leaves an effect unsure, when a retry could charge twice, when a saved change is published separately, or when spawned background work outlives its request.Votes: 0GitHub stars: 2
- Functional Making Illegal States UnrepresentableUse when a type can hold combinations the business forbids, when booleans, flags, or nullable fields encode state like loading and failed, or when code guards impossible values.Votes: 0GitHub stars: 2
- Functional Managing State ImmutablyUse when code mutates shared data or updates a record in place, when a concurrent update is lost or races, or when parallel work needs cancelling together.Votes: 0GitHub stars: 2
- Functional Modeling State MachinesUse when an entity has a lifecycle, when a status field drives branching, or when a function must ask what state a value is in before acting on it.Votes: 0GitHub stars: 2
- Functional Modeling With Algebraic TypesUse when designing domain types, when a record has many optional fields, or when choosing between a record, a union, and a bare primitive.Votes: 0GitHub stars: 2
- Functional Parameterizing DependenciesUse when domain code needs a database or clock, when tests need heavy mocking, or when an effect system or library makes simple code ceremonial.Votes: 0GitHub stars: 2
- Functional Programming StrategicallyUse when a deadline tempts a shortcut, when editing existing code, or when a codebase degrades a little with every change.Votes: 0GitHub stars: 2
- Functional Refactoring Toward Functional DesignUse when moving imperative or object-oriented code to functional design, when a code smell needs a move, or when a shape cannot absorb new requirements.Votes: 0GitHub stars: 2
- Functional Reviewing Functional DesignUse when asked to review a design, diff, component or module, before merging, judging a design standard, or when a flagged pattern may be a stated project convention.Votes: 0GitHub stars: 2
- Functional Separating LayersUse when adjacent layers repeat the same abstraction, when a function only forwards, when callers repeat the same lines after it, or when a utility carries a feature's policy.Votes: 0GitHub stars: 2
- Functional Separating Pure Core From ShellUse when business logic cannot be tested without I/O, when one call deep inside forces every caller to become async, or when deciding where a database or HTTP call belongs.Votes: 0GitHub stars: 2
- Functional Splitting And Joining CodeUse when deciding whether to split a function or module, when a boolean parameter selects behaviour, or when two pieces always change together.Votes: 0GitHub stars: 2
- Functional Testing Functional CodeUse when writing tests for functional code, when tests need heavy mocking or a database, when deciding what to test, or turning a claimed law into a property.Votes: 0GitHub stars: 2
- Functional Translating Gof PatternsUse when reaching for a factory, strategy, visitor or other class-based pattern, when porting object-oriented code, or when a pattern feels heavy.Votes: 0GitHub stars: 2
- Functional Typescript EffectUse when applying functional design in a TypeScript project built on the Effect library, including services, layers, schema boundaries, and tagged errors.Votes: 0GitHub stars: 2
- Functional Typescript React NextjsUse when placing logic across the server and client boundary in Next.js, writing a Server Action, invalidating a cache after a mutation, or deciding what may cross.Votes: 0GitHub stars: 2
- Functional Typescript ReactUse when a React component's props grow, when an effect computes state that render could derive, or when deciding what belongs in a global store and what a selector should.Votes: 0GitHub stars: 2
- Functional Typescript Ts PatternUse when a TypeScript project uses ts-pattern for matching, including exhaustive dispatch over unions, state machines, and Result handling.Votes: 0GitHub stars: 2
- Functional Typescript XstateUse when a lifecycle needs nested states, regions active at the same time, delayed transitions, or an actor per row, and whether a statechart beats a plain reducer.Votes: 0GitHub stars: 2
- Functional TypescriptUse when applying functional design in TypeScript without a functional library, including branded types, discriminated unions, and hand-rolled Result.Votes: 0GitHub stars: 2
- Functional Using Recursion And LazinessUse when a stack overflows, when data is too large to hold in memory, when an expensive result is recomputed, or when writing recursive functions.Votes: 0GitHub stars: 2
- Functional Writing Useful CommentsUse when writing or reviewing comments and documentation, when a comment restates the code, or when a contract cannot be expressed in a type.Votes: 0GitHub stars: 2