@nockdev/awf 6.2.0

package/.agent/skills/core/api-design/data/api-versioning.yaml

@@ -0,0 +1,217 @@
+metadata:
+  skill: api-design
+  domain: api_versioning
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: api-versioning.csv
+  patterns_count: 25
+  columns:
+  - id
+  - pattern
+  - description
+  - example
+  - pros
+  - cons
+  - level
+  - real_world
+patterns:
+- id: VER-01
+  pattern: URI Versioning
+  description: Version in URL path
+  example: /v1/users /v2/users
+  pros: Visible easy to implement cache-friendly
+  cons: Long URLs violates REST principle
+  level: BASIC
+  real_world: Facebook Twitter PayPal
+- id: VER-02
+  pattern: Header Versioning
+  description: Version in custom header
+  example: 'X-API-Version: 1'
+  pros: Clean URLs hide version
+  cons: Less discoverable browser testing hard
+  level: INTERMEDIATE
+  real_world: Microsoft Azure
+- id: VER-03
+  pattern: Query Param Version
+  description: Version as query parameter
+  example: /users?version=1
+  pros: Easy to add flexible
+  cons: Can be forgotten routing difficult
+  level: BASIC
+  real_world: Google Maps
+- id: VER-04
+  pattern: Media Type Version
+  description: Version in Accept header
+  example: 'Accept: application/vnd.api.v1+json'
+  pros: Fine-grained per-resource versioning
+  cons: Complex implementation client support
+  level: ADVANCED
+  real_world: GitHub Enterprise
+- id: VER-05
+  pattern: Semantic Versioning
+  description: MAJOR.MINOR.PATCH format
+  example: 2.1.0
+  pros: Clear change communication industry standard
+  cons: Maintenance overhead version explosion
+  level: BASIC
+  real_world: Twilio SDKs npm packages
+- id: VER-06
+  pattern: Date-Based Version
+  description: Version by release date
+  example: 2024-06-20 2026-01-28.acacia
+  pros: Clear timeline immutable snapshots
+  cons: Many versions accumulate naming long
+  level: INTERMEDIATE
+  real_world: Stripe GitHub REST API
+- id: VER-07
+  pattern: Calendar Versioning
+  description: YYYY-MM-DD in header
+  example: 'X-GitHub-Api-Version: 2022-11-28'
+  pros: Standard format long support window
+  cons: Requires header handling
+  level: INTERMEDIATE
+  real_world: GitHub REST API
+- id: VER-08
+  pattern: Major Breaking
+  description: Increment MAJOR for breaking
+  example: v1 → v2 when breaking change
+  pros: Clients know to update signals impact
+  cons: Requires migration guide
+  level: BASIC
+  real_world: All mature APIs
+- id: VER-09
+  pattern: Minor Features
+  description: Increment MINOR for features
+  example: v1.0 → v1.1 new endpoint
+  pros: Backward compatible safe to adopt
+  cons: Minor updates accumulate
+  level: BASIC
+  real_world: Twilio REST API
+- id: VER-10
+  pattern: Patch Fixes
+  description: Increment PATCH for fixes
+  example: v1.0.0 → v1.0.1 bug fix
+  pros: Safe to update minimal risk
+  cons: Frequent releases
+  level: BASIC
+  real_world: All SDKs
+- id: VER-11
+  pattern: Deprecation Notice
+  description: Warn before removing version
+  example: 'Deprecation: true header response field'
+  pros: Gives clients time to migrate
+  cons: Requires tracking enforcement
+  level: BASIC
+  real_world: Stripe Twilio
+- id: VER-12
+  pattern: Sunset Header
+  description: RFC 8594 removal date
+  example: 'Sunset: Sat 01 Jan 2027 00:00:00 GMT'
+  pros: Standard HTTP header machine-readable
+  cons: Client needs to check implement
+  level: INTERMEDIATE
+  real_world: Akamai Stripe
+- id: VER-13
+  pattern: Migration Guide
+  description: Document upgrade path
+  example: MIGRATION.md breaking-changes.md
+  pros: Helps clients upgrade reduces support
+  cons: Maintenance burden keep updated
+  level: BASIC
+  real_world: Stripe GitHub
+- id: VER-14
+  pattern: Parallel Versions
+  description: Run multiple versions simultaneously
+  example: Both /v1 and /v2 active for 24 months
+  pros: Smooth transition client flexibility
+  cons: Infrastructure cost maintenance burden
+  level: INTERMEDIATE
+  real_world: GitHub Stripe Twilio
+- id: VER-15
+  pattern: Feature Flags
+  description: Toggle features per client
+  example: 'X-Features: beta-search'
+  pros: Gradual rollout A/B testing
+  cons: Complex logic feature explosion
+  level: ADVANCED
+  real_world: LaunchDarkly pattern
+- id: VER-16
+  pattern: API Gateway Routing
+  description: Gateway routes to version backend
+  example: Kong/AWS API Gateway → v1 or v2
+  pros: Centralized routing version isolation
+  cons: Single point failure complexity
+  level: ADVANCED
+  real_world: Enterprise APIs
+- id: VER-17
+  pattern: SDK Version Pinning
+  description: Pin SDK to API version
+  example: stripe-python==5.0.0 pins 2024-06-20
+  pros: Stable integration predictable
+  cons: Must update SDK for new features
+  level: INTERMEDIATE
+  real_world: Stripe Twilio
+- id: VER-18
+  pattern: Account Version Pinning
+  description: Account pinned to first-use version
+  example: Account uses API version from first request
+  pros: Protected from breaking changes
+  cons: Must explicitly upgrade
+  level: ADVANCED
+  real_world: Stripe
+- id: VER-19
+  pattern: Version Override Header
+  description: Override default per-request
+  example: 'Stripe-Version: 2026-01-28'
+  pros: Test new version before upgrade
+  cons: Must remember to send header
+  level: INTERMEDIATE
+  real_world: Stripe
+- id: VER-20
+  pattern: Named Releases
+  description: Codename with date
+  example: 2024-09-30.acacia 2024-06-20.basil
+  pros: Human-friendly memorable
+  cons: Additional naming overhead
+  level: INTERMEDIATE
+  real_world: Stripe 2024+
+- id: VER-21
+  pattern: Changelog Automation
+  description: Auto-generate changelog
+  example: OpenAPI diff → CHANGELOG.md
+  pros: Accurate documentation less effort
+  cons: Requires tooling setup
+  level: INTERMEDIATE
+  real_world: Bump.sh Optic
+- id: VER-22
+  pattern: Breaking Change Detection
+  description: Automated compatibility check
+  example: buf breaking proto.lock
+  pros: Catch breaks before release
+  cons: False positives possible
+  level: ADVANCED
+  real_world: buf protolint
+- id: VER-23
+  pattern: Version Lifecycle
+  description: Defined support stages
+  example: Latest → Support → Deprecated → EOL
+  pros: Clear expectations planning
+  cons: Enforcement communication
+  level: INTERMEDIATE
+  real_world: Twilio
+- id: VER-24
+  pattern: Gradual Rollout
+  description: Progressive version adoption
+  example: 1% → 10% → 50% → 100% traffic
+  pros: Safe rollout quick rollback
+  cons: Complex infrastructure
+  level: ADVANCED
+  real_world: Google internal
+- id: VER-25
+  pattern: Version Negotiation
+  description: Client requests server negotiates
+  example: 'Accept: application/vnd.api.v2+json'
+  pros: Server backward compatible
+  cons: Complex server logic
+  level: ADVANCED
+  real_world: REST best practice

package/.agent/skills/core/api-design/data/error-responses.yaml

@@ -0,0 +1,135 @@
+metadata:
+  skill: api-design
+  domain: error_responses
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: error-responses.csv
+  patterns_count: 20
+  columns:
+  - id
+  - pattern
+  - description
+  - example
+  - rfc
+  - level
+patterns:
+- id: ERR-01
+  pattern: RFC 9457 Format
+  description: Standard problem details
+  example: '{type title status detail instance}'
+  rfc: RFC 9457
+  level: BASIC
+- id: ERR-02
+  pattern: Type URI
+  description: URI identifying problem type
+  example: 'type: https://api.example.com/errors/rate-limit'
+  rfc: RFC 9457
+  level: BASIC
+- id: ERR-03
+  pattern: Title
+  description: Short human-readable summary
+  example: 'title: "Rate Limit Exceeded"'
+  rfc: RFC 9457
+  level: BASIC
+- id: ERR-04
+  pattern: Status
+  description: HTTP status code in body
+  example: 'status: 429'
+  rfc: RFC 9457
+  level: BASIC
+- id: ERR-05
+  pattern: Detail
+  description: Specific occurrence explanation
+  example: 'detail: "You have exceeded 100 requests per minute"'
+  rfc: RFC 9457
+  level: BASIC
+- id: ERR-06
+  pattern: Instance
+  description: URI for this occurrence
+  example: 'instance: /logs/abc123'
+  rfc: RFC 9457
+  level: INTERMEDIATE
+- id: ERR-07
+  pattern: Content-Type
+  description: Problem details media type
+  example: 'Content-Type: application/problem+json'
+  rfc: RFC 9457
+  level: BASIC
+- id: ERR-08
+  pattern: Extension Members
+  description: Custom fields in response
+  example: '{...traceId: "abc" retryAfter: 60}'
+  rfc: RFC 9457
+  level: INTERMEDIATE
+- id: ERR-09
+  pattern: Validation Errors
+  description: Array of field errors
+  example: '{errors: [{field: "email" code: "invalid"}]}'
+  rfc: Custom
+  level: BASIC
+- id: ERR-10
+  pattern: Error Codes
+  description: Machine-readable error codes
+  example: '{code: "ERR_INVALID_EMAIL"}'
+  rfc: Custom
+  level: BASIC
+- id: ERR-11
+  pattern: Localized Messages
+  description: i18n error messages
+  example: '{message: "Invalid email" locale: "en"}'
+  rfc: Custom
+  level: INTERMEDIATE
+- id: ERR-12
+  pattern: Stack Trace Hidden
+  description: Never expose stack traces
+  example: Remove stack in production
+  rfc: Security
+  level: BASIC
+- id: ERR-13
+  pattern: Sensitive Data Hidden
+  description: Mask sensitive info in errors
+  example: Hide passwords tokens
+  rfc: Security
+  level: BASIC
+- id: ERR-14
+  pattern: Correlation ID
+  description: Link errors to logs
+  example: '{correlationId: "req-abc123"}'
+  rfc: Observability
+  level: INTERMEDIATE
+- id: ERR-15
+  pattern: Timestamp
+  description: Error occurrence time
+  example: '{timestamp: "2024-01-15T10:30:00Z"}'
+  rfc: Debugging
+  level: BASIC
+- id: ERR-16
+  pattern: Request ID
+  description: Unique request identifier
+  example: 'X-Request-ID: abc123'
+  rfc: Debugging
+  level: INTERMEDIATE
+- id: ERR-17
+  pattern: Documentation Link
+  description: Link to error docs
+  example: '{docs: "https://docs.api.com/errors/E001"}'
+  rfc: DX
+  level: INTERMEDIATE
+- id: ERR-18
+  pattern: Suggested Action
+  description: What client should do
+  example: '{action: "Retry after 60 seconds"}'
+  rfc: DX
+  level: ADVANCED
+- id: ERR-19
+  pattern: Partial Success
+  description: Return partial results with errors
+  example: '{data: [...] errors: [{index: 2}]}'
+  rfc: Bulk ops
+  level: ADVANCED
+- id: ERR-20
+  pattern: Error Hierarchy
+  description: Categorized error types
+  example: '{category: "validation" type: "field_error"}'
+  rfc: Organization
+  level: INTERMEDIATE

package/.agent/skills/core/api-design/data/graphql-patterns.yaml

@@ -0,0 +1,165 @@
+metadata:
+  skill: api-design
+  domain: graphql_patterns
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: graphql-patterns.csv
+  patterns_count: 25
+  columns:
+  - id
+  - pattern
+  - description
+  - example
+  - level
+  - category
+patterns:
+- id: GQL-01
+  pattern: PascalCase Types
+  description: Use PascalCase for type names
+  example: type User type OrderItem
+  level: BASIC
+  category: naming
+- id: GQL-02
+  pattern: camelCase Fields
+  description: Use camelCase for field names
+  example: firstName lastName createdAt
+  level: BASIC
+  category: naming
+- id: GQL-03
+  pattern: Domain-Driven Schema
+  description: Model schema around business domains
+  example: type Product type Inventory
+  level: BASIC
+  category: design
+- id: GQL-04
+  pattern: Strong Typing
+  description: Leverage type system fully
+  example: scalar DateTime enum Status
+  level: BASIC
+  category: design
+- id: GQL-05
+  pattern: Enum Finite Values
+  description: Use enums for fixed value sets
+  example: enum OrderStatus {PENDING SHIPPED}
+  level: BASIC
+  category: design
+- id: GQL-06
+  pattern: Interface Shared Fields
+  description: Use interfaces for common fields
+  example: 'interface Node { id: ID! }'
+  level: INTERMEDIATE
+  category: design
+- id: GQL-07
+  pattern: Union Polymorphism
+  description: Use unions for different types
+  example: union SearchResult = User | Product
+  level: INTERMEDIATE
+  category: design
+- id: GQL-08
+  pattern: Input Types Mutations
+  description: Use input types for mutations
+  example: input CreateUserInput { name email }
+  level: BASIC
+  category: mutations
+- id: GQL-09
+  pattern: Nullable by Default
+  description: Only use Non-Null when guaranteed
+  example: 'field: String vs field: String!'
+  level: INTERMEDIATE
+  category: design
+- id: GQL-10
+  pattern: Cursor Pagination
+  description: Use connection pattern for lists
+  example: first after last before edges
+  level: ADVANCED
+  category: pagination
+- id: GQL-11
+  pattern: Connection Pattern
+  description: Relay-style pagination
+  example: type UserConnection { edges pageInfo }
+  level: ADVANCED
+  category: pagination
+- id: GQL-12
+  pattern: Query Depth Limit
+  description: Prevent deeply nested queries
+  example: 'maxDepth: 7 in validation'
+  level: BASIC
+  category: security
+- id: GQL-13
+  pattern: Query Complexity
+  description: Limit query complexity score
+  example: 'complexityLimit: 1000'
+  level: INTERMEDIATE
+  category: security
+- id: GQL-14
+  pattern: Rate Limiting
+  description: Limit queries per time window
+  example: 100 queries per minute per user
+  level: BASIC
+  category: security
+- id: GQL-15
+  pattern: DataLoader Batching
+  description: Batch N+1 queries with DataLoader
+  example: userLoader.load(userId)
+  level: ADVANCED
+  category: performance
+- id: GQL-16
+  pattern: DataLoader Caching
+  description: Cache within single request
+  example: loader caches per request context
+  level: ADVANCED
+  category: performance
+- id: GQL-17
+  pattern: N+1 Detection
+  description: Detect N+1 query patterns
+  example: Monitoring resolver execution count
+  level: ADVANCED
+  category: performance
+- id: GQL-18
+  pattern: Context Object
+  description: Pass shared data via context
+  example: context.user context.db
+  level: BASIC
+  category: resolvers
+- id: GQL-19
+  pattern: Resolver Focus
+  description: Keep resolvers thin data-fetching
+  example: Extract logic to service layer
+  level: INTERMEDIATE
+  category: resolvers
+- id: GQL-20
+  pattern: Error Extensions
+  description: Add structured error data
+  example: 'extensions: { code field }'
+  level: INTERMEDIATE
+  category: errors
+- id: GQL-21
+  pattern: Partial Success
+  description: Return partial data with errors
+  example: 'data: {} errors: [{path}]'
+  level: INTERMEDIATE
+  category: errors
+- id: GQL-22
+  pattern: Deprecation
+  description: Use @deprecated directive
+  example: '@deprecated(reason: \"Use newField\")'
+  level: BASIC
+  category: evolution
+- id: GQL-23
+  pattern: Schema Documentation
+  description: Document types and fields
+  example: \"\"\"User account\"\"\" type User
+  level: BASIC
+  category: documentation
+- id: GQL-24
+  pattern: Persisted Queries
+  description: Cache query strings server-side
+  example: queryId hash instead of full query
+  level: ADVANCED
+  category: performance
+- id: GQL-25
+  pattern: HTTP Caching
+  description: Support GET with persisted queries
+  example: Cache-Control for read queries
+  level: ADVANCED
+  category: caching

package/.agent/skills/core/api-design/data/grpc-patterns.yaml

@@ -0,0 +1,165 @@
+metadata:
+  skill: api-design
+  domain: grpc_patterns
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: grpc-patterns.csv
+  patterns_count: 25
+  columns:
+  - id
+  - pattern
+  - description
+  - example
+  - level
+  - category
+patterns:
+- id: GRPC-01
+  pattern: Proto3 Syntax
+  description: Use proto3 for all .proto files
+  example: syntax = "proto3";
+  level: BASIC
+  category: protobuf
+- id: GRPC-02
+  pattern: Package Naming
+  description: Use reverse domain package names
+  example: package com.example.api.v1;
+  level: BASIC
+  category: protobuf
+- id: GRPC-03
+  pattern: Message Naming
+  description: Use PascalCase for messages
+  example: message UserRequest
+  level: BASIC
+  category: naming
+- id: GRPC-04
+  pattern: Field Naming
+  description: Use snake_case for fields
+  example: string user_name = 1;
+  level: BASIC
+  category: naming
+- id: GRPC-05
+  pattern: Enum Naming
+  description: SCREAMING_SNAKE for enum values
+  example: enum Status { STATUS_UNSPECIFIED = 0; }
+  level: BASIC
+  category: naming
+- id: GRPC-06
+  pattern: Unspecified Enum
+  description: First enum value is UNSPECIFIED = 0
+  example: STATUS_UNSPECIFIED = 0;
+  level: BASIC
+  category: protobuf
+- id: GRPC-07
+  pattern: Reserved Tags
+  description: Never reuse deleted field tags
+  example: reserved 2 15 to 17;
+  level: INTERMEDIATE
+  category: protobuf
+- id: GRPC-08
+  pattern: Reserved Names
+  description: Reserve deleted field names
+  example: reserved "old_field" "legacy";
+  level: INTERMEDIATE
+  category: protobuf
+- id: GRPC-09
+  pattern: Field Immutability
+  description: Never change field types after deploy
+  example: int32 to int64 breaks clients
+  level: INTERMEDIATE
+  category: protobuf
+- id: GRPC-10
+  pattern: Well-Known Types
+  description: Use google well-known types
+  example: google.protobuf.Timestamp
+  level: BASIC
+  category: protobuf
+- id: GRPC-11
+  pattern: Unary RPC
+  description: Single request single response
+  example: rpc GetUser(UserRequest) returns (User)
+  level: BASIC
+  category: rpc
+- id: GRPC-12
+  pattern: Server Streaming
+  description: Single request stream response
+  example: rpc ListUsers(Empty) returns (stream User)
+  level: INTERMEDIATE
+  category: streaming
+- id: GRPC-13
+  pattern: Client Streaming
+  description: Stream request single response
+  example: rpc UploadData(stream Chunk) returns (Status)
+  level: INTERMEDIATE
+  category: streaming
+- id: GRPC-14
+  pattern: Bidirectional Stream
+  description: Both sides stream
+  example: rpc Chat(stream Msg) returns (stream Msg)
+  level: ADVANCED
+  category: streaming
+- id: GRPC-15
+  pattern: Deadlines
+  description: Always set RPC deadlines
+  example: ctx WithTimeout(ctx 5*time.Second)
+  level: BASIC
+  category: reliability
+- id: GRPC-16
+  pattern: Keepalive Pings
+  description: Maintain HTTP/2 connections
+  example: 'keepalive.ClientParameters{Time: 10s}'
+  level: INTERMEDIATE
+  category: reliability
+- id: GRPC-17
+  pattern: Channel Reuse
+  description: Reuse gRPC channels
+  example: Single channel per service
+  level: BASIC
+  category: performance
+- id: GRPC-18
+  pattern: Channel Pooling
+  description: Pool channels under high load
+  example: Multiple channels for load distribution
+  level: ADVANCED
+  category: performance
+- id: GRPC-19
+  pattern: Interceptors
+  description: Cross-cutting via interceptors
+  example: Logging auth interceptors
+  level: INTERMEDIATE
+  category: patterns
+- id: GRPC-20
+  pattern: Error Codes
+  description: Use gRPC status codes
+  example: codes.NotFound codes.InvalidArgument
+  level: BASIC
+  category: errors
+- id: GRPC-21
+  pattern: Error Details
+  description: Add structured error details
+  example: status.WithDetails(errInfo)
+  level: INTERMEDIATE
+  category: errors
+- id: GRPC-22
+  pattern: Service Versioning
+  description: Version in package name
+  example: package api.v1; package api.v2;
+  level: BASIC
+  category: versioning
+- id: GRPC-23
+  pattern: Backward Compatible
+  description: Add fields don't remove
+  example: New optional fields are safe
+  level: INTERMEDIATE
+  category: versioning
+- id: GRPC-24
+  pattern: mTLS Auth
+  description: Mutual TLS for security
+  example: grpc.WithTransportCredentials(creds)
+  level: ADVANCED
+  category: security
+- id: GRPC-25
+  pattern: Buf Lint
+  description: Use buf lint for proto files
+  example: buf lint buf format buf breaking
+  level: INTERMEDIATE
+  category: tooling