@nockdev/awf 6.2.0

package/.agent/skills/core/api-design/data/http-status-codes.yaml

@@ -0,0 +1,176 @@
+metadata:
+  skill: api-design
+  domain: http_status_codes
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: http-status-codes.csv
+  patterns_count: 27
+  columns:
+  - code
+  - category
+  - description
+  - example_use
+  - level
+patterns:
+- id: item_001
+  code: '200'
+  category: Success
+  description: OK - Request succeeded
+  example_use: GET resource returned
+  level: BASIC
+- id: item_002
+  code: '201'
+  category: Success
+  description: Created - Resource created
+  example_use: POST new resource
+  level: BASIC
+- id: item_003
+  code: '202'
+  category: Success
+  description: Accepted - Processing async
+  example_use: Long-running job started
+  level: INTERMEDIATE
+- id: item_004
+  code: '204'
+  category: Success
+  description: No Content - Success no body
+  example_use: DELETE successful
+  level: BASIC
+- id: item_005
+  code: '206'
+  category: Success
+  description: Partial Content - Range request
+  example_use: Video streaming
+  level: ADVANCED
+- id: item_006
+  code: '301'
+  category: Redirect
+  description: Moved Permanently
+  example_use: Resource URL changed
+  level: BASIC
+- id: item_007
+  code: '302'
+  category: Redirect
+  description: Found - Temporary redirect
+  example_use: OAuth callback
+  level: BASIC
+- id: item_008
+  code: '304'
+  category: Redirect
+  description: Not Modified - Cache valid
+  example_use: ETag validation
+  level: INTERMEDIATE
+- id: item_009
+  code: '307'
+  category: Redirect
+  description: Temporary Redirect - Keep method
+  example_use: Temporary move
+  level: INTERMEDIATE
+- id: item_010
+  code: '308'
+  category: Redirect
+  description: Permanent Redirect - Keep method
+  example_use: Permanent move
+  level: INTERMEDIATE
+- id: item_011
+  code: '400'
+  category: Client Error
+  description: Bad Request - Invalid syntax
+  example_use: Malformed JSON
+  level: BASIC
+- id: item_012
+  code: '401'
+  category: Client Error
+  description: Unauthorized - Auth required
+  example_use: Missing/invalid token
+  level: BASIC
+- id: item_013
+  code: '403'
+  category: Client Error
+  description: Forbidden - No permission
+  example_use: Insufficient privileges
+  level: BASIC
+- id: item_014
+  code: '404'
+  category: Client Error
+  description: Not Found - Resource missing
+  example_use: Invalid resource ID
+  level: BASIC
+- id: item_015
+  code: '405'
+  category: Client Error
+  description: Method Not Allowed
+  example_use: POST on read-only
+  level: BASIC
+- id: item_016
+  code: '406'
+  category: Client Error
+  description: Not Acceptable - Content-Type
+  example_use: Accept header mismatch
+  level: INTERMEDIATE
+- id: item_017
+  code: '408'
+  category: Client Error
+  description: Request Timeout
+  example_use: Client too slow
+  level: INTERMEDIATE
+- id: item_018
+  code: '409'
+  category: Client Error
+  description: Conflict - State conflict
+  example_use: Duplicate resource
+  level: BASIC
+- id: item_019
+  code: '410'
+  category: Client Error
+  description: Gone - Permanently removed
+  example_use: Deleted resource
+  level: INTERMEDIATE
+- id: item_020
+  code: '415'
+  category: Client Error
+  description: Unsupported Media Type
+  example_use: Wrong Content-Type
+  level: BASIC
+- id: item_021
+  code: '422'
+  category: Client Error
+  description: Unprocessable Entity
+  example_use: Validation failed
+  level: BASIC
+- id: item_022
+  code: '429'
+  category: Client Error
+  description: Too Many Requests
+  example_use: Rate limit exceeded
+  level: BASIC
+- id: item_023
+  code: '500'
+  category: Server Error
+  description: Internal Server Error
+  example_use: Unexpected error
+  level: BASIC
+- id: item_024
+  code: '501'
+  category: Server Error
+  description: Not Implemented
+  example_use: Feature not ready
+  level: INTERMEDIATE
+- id: item_025
+  code: '502'
+  category: Server Error
+  description: Bad Gateway
+  example_use: Upstream error
+  level: INTERMEDIATE
+- id: item_026
+  code: '503'
+  category: Server Error
+  description: Service Unavailable
+  example_use: Maintenance mode
+  level: BASIC
+- id: item_027
+  code: '504'
+  category: Server Error
+  description: Gateway Timeout
+  example_use: Upstream timeout
+  level: INTERMEDIATE

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

@@ -0,0 +1,121 @@
+metadata:
+  skill: api-design
+  domain: pagination
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: pagination.csv
+  patterns_count: 15
+  columns:
+  - id
+  - pattern
+  - description
+  - example
+  - pros
+  - cons
+  - use_case
+patterns:
+- id: PAG-01
+  pattern: Offset Pagination
+  description: Skip N records take M
+  example: ?offset=20&limit=10
+  pros: Simple random access
+  cons: Slow at large offsets
+  use_case: Small static data
+- id: PAG-02
+  pattern: Page Number
+  description: Page and size params
+  example: ?page=3&pageSize=10
+  pros: Intuitive for users
+  cons: Same issues as offset
+  use_case: Admin interfaces
+- id: PAG-03
+  pattern: Cursor Pagination
+  description: Opaque cursor for position
+  example: ?cursor=eyJpZCI6MTIz
+  pros: Efficient consistent
+  cons: No random access
+  use_case: Large dynamic data
+- id: PAG-04
+  pattern: Keyset Pagination
+  description: Last seen key values
+  example: ?after_id=123&limit=10
+  pros: Very efficient stable
+  cons: Sequential only
+  use_case: Ordered lists logs
+- id: PAG-05
+  pattern: Relay Connection
+  description: GraphQL connection spec
+  example: first after edges pageInfo
+  pros: Standard spec
+  cons: Complex implementation
+  use_case: GraphQL APIs
+- id: PAG-06
+  pattern: Total Count
+  description: Include total in response
+  example: '{total: 100 page: 1}'
+  pros: User knows position
+  cons: Expensive query
+  use_case: Small datasets
+- id: PAG-07
+  pattern: Has Next Page
+  description: Boolean for more data
+  example: '{hasNext: true data: []}'
+  pros: Avoids count query
+  cons: No total info
+  use_case: Large datasets
+- id: PAG-08
+  pattern: Link Headers
+  description: RFC 5988 pagination links
+  example: 'Link: <url>; rel="next"'
+  pros: Standard HTTP
+  cons: Header parsing
+  use_case: REST APIs
+- id: PAG-09
+  pattern: Envelope Links
+  description: Links in response body
+  example: '{_links: {next prev}}'
+  pros: Self-documenting
+  cons: Larger response
+  use_case: HATEOAS APIs
+- id: PAG-10
+  pattern: Default Page Size
+  description: Sensible default limit
+  example: 'Default: 20 Max: 100'
+  pros: Predictable behavior
+  cons: May not fit all
+  use_case: All APIs
+- id: PAG-11
+  pattern: Max Page Size
+  description: Cap maximum page size
+  example: Max 100 even if 1000 requested
+  pros: Prevents abuse
+  cons: Client limits
+  use_case: Public APIs
+- id: PAG-12
+  pattern: Consistent Ordering
+  description: Stable sort for pagination
+  example: ORDER BY created_at id
+  pros: Prevents duplicates
+  cons: Requires unique key
+  use_case: All pagination
+- id: PAG-13
+  pattern: Cursor Encoding
+  description: Encode cursor as base64
+  example: base64(JSON.stringify(pos))
+  pros: Opaque to client
+  cons: Decode overhead
+  use_case: Cursor pagination
+- id: PAG-14
+  pattern: Time-Based Cursor
+  description: Timestamp in cursor
+  example: ?since=2024-01-01T00:00:00Z
+  pros: Good for feeds
+  cons: Clock sync issues
+  use_case: Activity feeds
+- id: PAG-15
+  pattern: Seek Method
+  description: SQL SEEK instead of OFFSET
+  example: WHERE id > last_id
+  pros: Database efficient
+  cons: Requires indexed key
+  use_case: Large tables

package/.agent/skills/core/api-design/data/rate-limiting.yaml

@@ -0,0 +1,135 @@
+metadata:
+  skill: api-design
+  domain: rate_limiting
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: rate-limiting.csv
+  patterns_count: 20
+  columns:
+  - id
+  - pattern
+  - description
+  - example
+  - algorithm
+  - use_case
+patterns:
+- id: RL-01
+  pattern: Token Bucket
+  description: Tokens added at fixed rate
+  example: 10 tokens/sec 100 burst
+  algorithm: Bucket fills refills on use
+  use_case: Handles bursts
+- id: RL-02
+  pattern: Leaky Bucket
+  description: Fixed rate output queue
+  example: Process 10 req/sec always
+  algorithm: Queue drains at constant rate
+  use_case: Smooth traffic
+- id: RL-03
+  pattern: Fixed Window
+  description: Count per time window
+  example: 100 req per minute window
+  algorithm: Reset count each window
+  use_case: Simple implementation
+- id: RL-04
+  pattern: Sliding Window Log
+  description: Track each request timestamp
+  example: Log all requests compute rate
+  algorithm: Precise but memory heavy
+  use_case: Accuracy needed
+- id: RL-05
+  pattern: Sliding Window Counter
+  description: Weighted window estimate
+  example: Weight previous + current
+  algorithm: Balance accuracy memory
+  use_case: Most APIs
+- id: RL-06
+  pattern: 429 Status
+  description: Return Too Many Requests
+  example: HTTP 429 Too Many Requests
+  algorithm: Standard HTTP
+  use_case: All rate limits
+- id: RL-07
+  pattern: Retry-After Header
+  description: Indicate wait time
+  example: 'Retry-After: 60'
+  algorithm: Seconds or HTTP-date
+  use_case: After 429
+- id: RL-08
+  pattern: X-RateLimit-Limit
+  description: Show limit value
+  example: 'X-RateLimit-Limit: 100'
+  algorithm: Custom header
+  use_case: Rate info
+- id: RL-09
+  pattern: X-RateLimit-Remaining
+  description: Show remaining requests
+  example: 'X-RateLimit-Remaining: 45'
+  algorithm: Custom header
+  use_case: Rate info
+- id: RL-10
+  pattern: X-RateLimit-Reset
+  description: Show reset timestamp
+  example: 'X-RateLimit-Reset: 1640000000'
+  algorithm: Unix timestamp
+  use_case: Rate info
+- id: RL-11
+  pattern: Per-User Limits
+  description: Rate limit by user ID
+  example: 100 req/min per user
+  algorithm: User identification
+  use_case: Authenticated APIs
+- id: RL-12
+  pattern: Per-IP Limits
+  description: Rate limit by IP address
+  example: 50 req/min per IP
+  algorithm: IP extraction
+  use_case: Public APIs
+- id: RL-13
+  pattern: Per-Endpoint Limits
+  description: Different limits per route
+  example: '/search: 10/min /users: 100/min'
+  algorithm: Endpoint config
+  use_case: Expensive endpoints
+- id: RL-14
+  pattern: Tiered Limits
+  description: Limits by subscription
+  example: 'Free: 100 Pro: 10000'
+  algorithm: Tier lookup
+  use_case: SaaS APIs
+- id: RL-15
+  pattern: Exponential Backoff
+  description: Client retry strategy
+  example: Wait 1s 2s 4s 8s...
+  algorithm: Client-side
+  use_case: When 429 received
+- id: RL-16
+  pattern: Jitter
+  description: Add randomness to retry
+  example: backoff + random(0 100ms)
+  algorithm: Prevents thundering herd
+  use_case: Distributed clients
+- id: RL-17
+  pattern: Circuit Breaker
+  description: Stop requests when failing
+  example: Open after 5 failures
+  algorithm: Client-side protection
+  use_case: Unreliable backends
+- id: RL-18
+  pattern: Quota Management
+  description: Track usage over period
+  example: 1000 calls/day quota
+  algorithm: Daily/monthly tracking
+  use_case: Metered APIs
+- id: RL-19
+  pattern: Rate Limit Bypass
+  description: Whitelist trusted clients
+  example: Skip limits for internal
+  algorithm: Secret header/IP
+  use_case: Internal services
+- id: RL-20
+  pattern: Distributed Rate Limit
+  description: Shared state across nodes
+  example: Redis counter cluster
+  algorithm: Centralized counter
+  use_case: Scaled APIs

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

@@ -0,0 +1,195 @@
+metadata:
+  skill: api-design
+  domain: rest_patterns
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: rest-patterns.csv
+  patterns_count: 30
+  columns:
+  - id
+  - pattern
+  - description
+  - example
+  - level
+  - category
+patterns:
+- id: REST-01
+  pattern: Resource Naming
+  description: Use plural nouns for resource collections
+  example: /users /products /orders
+  level: BASIC
+  category: uri
+- id: REST-02
+  pattern: Hierarchical URIs
+  description: Nest related resources max 2-3 levels
+  example: /users/{id}/orders/{orderId}
+  level: BASIC
+  category: uri
+- id: REST-03
+  pattern: Hyphen Separation
+  description: Use hyphens for multi-word resources
+  example: /order-items /user-profiles
+  level: BASIC
+  category: uri
+- id: REST-04
+  pattern: Lowercase URIs
+  description: Keep URIs lowercase for consistency
+  example: /users not /Users
+  level: BASIC
+  category: uri
+- id: REST-05
+  pattern: No Verbs in URI
+  description: HTTP methods imply action
+  example: GET /users not /getUsers
+  level: BASIC
+  category: uri
+- id: REST-06
+  pattern: Query Parameters Filter
+  description: Use query params for filtering
+  example: /users?status=active&role=admin
+  level: BASIC
+  category: query
+- id: REST-07
+  pattern: Query Parameters Sort
+  description: Use sort param with field:direction
+  example: /products?sort=price:desc
+  level: BASIC
+  category: query
+- id: REST-08
+  pattern: GET Idempotent
+  description: GET should not modify state
+  example: GET /users returns same result
+  level: BASIC
+  category: methods
+- id: REST-09
+  pattern: POST Create
+  description: POST creates new resources
+  example: POST /users creates user
+  level: BASIC
+  category: methods
+- id: REST-10
+  pattern: PUT Replace
+  description: PUT replaces entire resource
+  example: PUT /users/1 replaces user 1
+  level: BASIC
+  category: methods
+- id: REST-11
+  pattern: PATCH Partial
+  description: PATCH updates specific fields
+  example: 'PATCH /users/1 {name: ''new''}'
+  level: BASIC
+  category: methods
+- id: REST-12
+  pattern: DELETE Remove
+  description: DELETE removes resource
+  example: DELETE /users/1 removes user 1
+  level: BASIC
+  category: methods
+- id: REST-13
+  pattern: RMM Level 0
+  description: Single URI single HTTP method (RPC style)
+  example: POST /api with action in body
+  level: MATURITY
+  category: richardson
+- id: REST-14
+  pattern: RMM Level 1
+  description: Individual resources with unique URIs
+  example: /doctors/1 /appointments/2
+  level: MATURITY
+  category: richardson
+- id: REST-15
+  pattern: RMM Level 2
+  description: Proper HTTP verbs for operations
+  example: GET/POST/PUT/DELETE per resource
+  level: MATURITY
+  category: richardson
+- id: REST-16
+  pattern: RMM Level 3
+  description: HATEOAS hypermedia controls
+  example: Links in response for navigation
+  level: MATURITY
+  category: richardson
+- id: REST-17
+  pattern: HATEOAS Links
+  description: Include navigation links in response
+  example: '{data: {} _links: {self next}}'
+  level: ADVANCED
+  category: hateoas
+- id: REST-18
+  pattern: HATEOAS Actions
+  description: Include available actions in response
+  example: '{_actions: [{rel: ''cancel'' method: ''POST''}]}'
+  level: ADVANCED
+  category: hateoas
+- id: REST-19
+  pattern: Self-Discovery
+  description: Single entry point discovers API
+  example: GET / returns all resource links
+  level: ADVANCED
+  category: hateoas
+- id: REST-20
+  pattern: Content Negotiation
+  description: Use Accept header for format
+  example: 'Accept: application/json'
+  level: INTERMEDIATE
+  category: headers
+- id: REST-21
+  pattern: ETag Caching
+  description: Use ETag for cache validation
+  example: 'ETag: "abc123" If-None-Match'
+  level: INTERMEDIATE
+  category: caching
+- id: REST-22
+  pattern: Cache-Control
+  description: Set caching directives
+  example: 'Cache-Control: max-age=3600'
+  level: INTERMEDIATE
+  category: caching
+- id: REST-23
+  pattern: Conditional GET
+  description: Support If-Modified-Since
+  example: 'If-Modified-Since: date 304 response'
+  level: INTERMEDIATE
+  category: caching
+- id: REST-24
+  pattern: Stateless Requests
+  description: Each request contains all info
+  example: No server-side session state
+  level: BASIC
+  category: principles
+- id: REST-25
+  pattern: JSON Preferred
+  description: Use JSON over XML for data
+  example: 'Content-Type: application/json'
+  level: BASIC
+  category: format
+- id: REST-26
+  pattern: Consistent Naming
+  description: Use camelCase or snake_case consistently
+  example: userName or user_name not mixed
+  level: BASIC
+  category: format
+- id: REST-27
+  pattern: Collection Envelope
+  description: Wrap collections with metadata
+  example: '{data: [] meta: {total page}}'
+  level: INTERMEDIATE
+  category: format
+- id: REST-28
+  pattern: Sparse Fieldsets
+  description: Allow clients to select fields
+  example: /users?fields=id
+  level: name
+  category: email
+- id: REST-29
+  pattern: Field Expansion
+  description: Allow nested resource expansion
+  example: /users?expand=orders
+  level: profile
+  category: INTERMEDIATE
+- id: REST-30
+  pattern: Bulk Operations
+  description: Support batch create/update/delete
+  example: POST /users/bulk [{} {} {}]
+  level: ADVANCED
+  category: operations