@fprad0/skill-master-mcp 0.0.10 → 0.0.11

package/docs/skill-candidates/v0.0.11/nextjs/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Next.js"
+  short_description: "Next.js App Router expert guidance"

package/docs/skill-candidates/v0.0.11/nextjs/references/app-router-files.md

@@ -0,0 +1,94 @@
+# Next.js App Router — File Convention Reference
+
+## Special Files
+
+| File | Purpose | Server/Client |
+|------|---------|---------------|
+| `layout.tsx` | Shared UI wrapper, preserves state | Server (default) |
+| `page.tsx` | Unique route UI | Server (default) |
+| `loading.tsx` | Suspense fallback | Server (default) |
+| `error.tsx` | Error boundary | Client (required) |
+| `not-found.tsx` | 404 UI | Server (default) |
+| `route.ts` | API endpoint (Route Handler) | Server only |
+| `template.tsx` | Layout that remounts on navigation | Server (default) |
+| `default.tsx` | Parallel route fallback | Server (default) |
+| `proxy.ts` | Network proxy (replaces middleware) | Server (Node.js) |
+| `opengraph-image.tsx` | Auto-generated OG image for route | Server (Edge) |
+| `twitter-image.tsx` | Auto-generated Twitter card image | Server (Edge) |
+
+## Route Segments
+
+| Pattern | Example | Matches |
+|---------|---------|---------|
+| `[id]` | `app/users/[id]/page.tsx` | `/users/123` |
+| `[...slug]` | `app/docs/[...slug]/page.tsx` | `/docs/a/b/c` |
+| `[[...slug]]` | `app/shop/[[...slug]]/page.tsx` | `/shop` or `/shop/a/b` |
+| `(group)` | `app/(marketing)/page.tsx` | `/` (group ignored in URL) |
+| `@slot` | `app/@sidebar/page.tsx` | Parallel route slot |
+
+## Data Fetching Patterns
+
+### Server Component (Default)
+```tsx
+export default async function Page() {
+  const data = await fetch('https://api.example.com/data')
+  return <div>{data}</div>
+}
+```
+
+### With Params (Async in Next.js 16)
+```tsx
+export default async function Page({
+  params,
+}: {
+  params: Promise<{ id: string }>
+}) {
+  const { id } = await params
+  const user = await getUser(id)
+  return <UserProfile user={user} />
+}
+```
+
+### With Search Params (Async in Next.js 16)
+```tsx
+export default async function Page({
+  searchParams,
+}: {
+  searchParams: Promise<{ q?: string }>
+}) {
+  const { q } = await searchParams
+  const results = await search(q)
+  return <SearchResults results={results} />
+}
+```
+
+### generateStaticParams (SSG)
+```tsx
+export async function generateStaticParams() {
+  const posts = await getPosts()
+  return posts.map((post) => ({ slug: post.slug }))
+}
+
+export default async function Page({
+  params,
+}: {
+  params: Promise<{ slug: string }>
+}) {
+  const { slug } = await params
+  const post = await getPost(slug)
+  return <Post post={post} />
+}
+```
+
+### generateMetadata
+```tsx
+export async function generateMetadata({
+  params,
+}: {
+  params: Promise<{ id: string }>
+}) {
+  const { id } = await params
+  const product = await getProduct(id)
+  return { title: product.name, description: product.description }
+}
+```

package/docs/skill-candidates/v0.0.11/python-engineering/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: python-engineering
+description: "Design, implement, review and debug Python services, CLIs, automation, APIs, scripts, packaging and runtime behavior with practical attention to typing, environments, tests and production safety."
+---
+
+# Python Engineering
+
+Use this skill when a task is primarily about Python code, tooling or runtime behavior.
+
+## Workflow
+
+- Inspect the real Python entrypoint, environment and dependency model before editing.
+- Identify whether the task is service, CLI, automation, library, notebook or data script work.
+- Keep I/O boundaries explicit: args, env vars, files, HTTP, queues and database calls.
+- Prefer simple module boundaries, type hints where they help, and predictable error handling.
+- Validate with one-shot commands, tests or smoke scripts instead of long-running processes.
+
+## Coverage
+
+- Python services, CLIs, scripts, packaging, virtualenv/uv/pip workflows and automation.
+- Typing, logging, error handling, serialization, subprocesses and background jobs.
+- Refactors, debugging, code review, reliability hardening and operational scripts.
+
+## Reference Anchors
+
+- Python docs: `https://docs.python.org/3/`
+- Packaging guide: `https://packaging.python.org/`
+
+## Guardrails
+
+- Do not mix environment management strategies blindly inside the same project.
+- Do not hide runtime import errors behind broad exception handlers.
+- Do not add heavy dependencies when the standard library is enough.
+- Do not claim reproducibility without validating the real environment path.

package/docs/skill-candidates/v0.0.11/ruby-engineering/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: ruby-engineering
+description: "Implement and review Ruby applications, scripts and services with practical focus on readability, gem hygiene, CLI/runtime behavior, tests, data handling and operational reliability."
+---
+
+# Ruby Engineering
+
+Use this skill when the task is predominantly Ruby code or Ruby-based tooling.
+
+## Workflow
+
+- Confirm whether the project is script-first, gem-based, Rails-adjacent or service-oriented.
+- Read Gemfile, runtime version and command entrypoints before changing behavior.
+- Favor clear object boundaries, simple flows and expressive error handling.
+- Keep side effects isolated and validate with direct CLI or test execution.
+- Match the existing Ruby style instead of forcing foreign patterns.
+
+## Coverage
+
+- Ruby scripts, services, gems, automation, CLI tools and app internals.
+- Bundler, dependency hygiene, serialization, file and process workflows.
+- Debugging, refactoring, code review and runtime hardening.
+
+## Reference Anchors
+
+- Ruby docs: `https://www.ruby-lang.org/en/documentation/`
+- Ruby core reference: `https://docs.ruby-lang.org/en/`
+
+## Guardrails
+
+- Do not introduce meta-programming where plain code is clearer.
+- Do not ignore Ruby version compatibility.
+- Do not hide shell or file side effects from operators.
+- Do not add gems for trivial standard-library tasks.

package/docs/skill-candidates/v0.0.11/senior-fullstack/SKILL.md

@@ -0,0 +1,209 @@
+---
+name: senior-fullstack
+description: Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.
+---
+
+# Senior Fullstack
+
+Complete toolkit for senior fullstack with modern tools and best practices.
+
+## Quick Start
+
+### Main Capabilities
+
+This skill provides three core capabilities through automated scripts:
+
+```bash
+# Script 1: Fullstack Scaffolder
+python scripts/fullstack_scaffolder.py [options]
+
+# Script 2: Project Scaffolder
+python scripts/project_scaffolder.py [options]
+
+# Script 3: Code Quality Analyzer
+python scripts/code_quality_analyzer.py [options]
+```
+
+## Core Capabilities
+
+### 1. Fullstack Scaffolder
+
+Automated tool for fullstack scaffolder tasks.
+
+**Features:**
+- Automated scaffolding
+- Best practices built-in
+- Configurable templates
+- Quality checks
+
+**Usage:**
+```bash
+python scripts/fullstack_scaffolder.py <project-path> [options]
+```
+
+### 2. Project Scaffolder
+
+Comprehensive analysis and optimization tool.
+
+**Features:**
+- Deep analysis
+- Performance metrics
+- Recommendations
+- Automated fixes
+
+**Usage:**
+```bash
+python scripts/project_scaffolder.py <target-path> [--verbose]
+```
+
+### 3. Code Quality Analyzer
+
+Advanced tooling for specialized tasks.
+
+**Features:**
+- Expert-level automation
+- Custom configurations
+- Integration ready
+- Production-grade output
+
+**Usage:**
+```bash
+python scripts/code_quality_analyzer.py [arguments] [options]
+```
+
+## Reference Documentation
+
+### Tech Stack Guide
+
+Comprehensive guide available in `references/tech_stack_guide.md`:
+
+- Detailed patterns and practices
+- Code examples
+- Best practices
+- Anti-patterns to avoid
+- Real-world scenarios
+
+### Architecture Patterns
+
+Complete workflow documentation in `references/architecture_patterns.md`:
+
+- Step-by-step processes
+- Optimization strategies
+- Tool integrations
+- Performance tuning
+- Troubleshooting guide
+
+### Development Workflows
+
+Technical reference guide in `references/development_workflows.md`:
+
+- Technology stack details
+- Configuration examples
+- Integration patterns
+- Security considerations
+- Scalability guidelines
+
+## Tech Stack
+
+**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin
+**Frontend:** React, Next.js, React Native, Flutter
+**Backend:** Node.js, Express, GraphQL, REST APIs
+**Database:** PostgreSQL, Prisma, NeonDB, Supabase
+**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI
+**Cloud:** AWS, GCP, Azure
+
+## Development Workflow
+
+### 1. Setup and Configuration
+
+```bash
+# Install dependencies
+npm install
+# or
+pip install -r requirements.txt
+
+# Configure environment
+cp .env.example .env
+```
+
+### 2. Run Quality Checks
+
+```bash
+# Use the analyzer script
+python scripts/project_scaffolder.py .
+
+# Review recommendations
+# Apply fixes
+```
+
+### 3. Implement Best Practices
+
+Follow the patterns and practices documented in:
+- `references/tech_stack_guide.md`
+- `references/architecture_patterns.md`
+- `references/development_workflows.md`
+
+## Best Practices Summary
+
+### Code Quality
+- Follow established patterns
+- Write comprehensive tests
+- Document decisions
+- Review regularly
+
+### Performance
+- Measure before optimizing
+- Use appropriate caching
+- Optimize critical paths
+- Monitor in production
+
+### Security
+- Validate all inputs
+- Use parameterized queries
+- Implement proper authentication
+- Keep dependencies updated
+
+### Maintainability
+- Write clear code
+- Use consistent naming
+- Add helpful comments
+- Keep it simple
+
+## Common Commands
+
+```bash
+# Development
+npm run dev
+npm run build
+npm run test
+npm run lint
+
+# Analysis
+python scripts/project_scaffolder.py .
+python scripts/code_quality_analyzer.py --analyze
+
+# Deployment
+docker build -t app:latest .
+docker-compose up -d
+kubectl apply -f k8s/
+```
+
+## Troubleshooting
+
+### Common Issues
+
+Check the comprehensive troubleshooting section in `references/development_workflows.md`.
+
+### Getting Help
+
+- Review reference documentation
+- Check script output messages
+- Consult tech stack documentation
+- Review error logs
+
+## Resources
+
+- Pattern Reference: `references/tech_stack_guide.md`
+- Workflow Guide: `references/architecture_patterns.md`
+- Technical Guide: `references/development_workflows.md`
+- Tool Scripts: `scripts/` directory

package/docs/skill-candidates/v0.0.11/senior-fullstack/references/architecture_patterns.md

@@ -0,0 +1,103 @@
+# Architecture Patterns
+
+## Overview
+
+This reference guide provides comprehensive information for senior fullstack.
+
+## Patterns and Practices
+
+### Pattern 1: Best Practice Implementation
+
+**Description:**
+Detailed explanation of the pattern.
+
+**When to Use:**
+- Scenario 1
+- Scenario 2
+- Scenario 3
+
+**Implementation:**
+```typescript
+// Example code implementation
+export class Example {
+  // Implementation details
+}
+```
+
+**Benefits:**
+- Benefit 1
+- Benefit 2
+- Benefit 3
+
+**Trade-offs:**
+- Consider 1
+- Consider 2
+- Consider 3
+
+### Pattern 2: Advanced Technique
+
+**Description:**
+Another important pattern for senior fullstack.
+
+**Implementation:**
+```typescript
+// Advanced example
+async function advancedExample() {
+  // Code here
+}
+```
+
+## Guidelines
+
+### Code Organization
+- Clear structure
+- Logical separation
+- Consistent naming
+- Proper documentation
+
+### Performance Considerations
+- Optimization strategies
+- Bottleneck identification
+- Monitoring approaches
+- Scaling techniques
+
+### Security Best Practices
+- Input validation
+- Authentication
+- Authorization
+- Data protection
+
+## Common Patterns
+
+### Pattern A
+Implementation details and examples.
+
+### Pattern B
+Implementation details and examples.
+
+### Pattern C
+Implementation details and examples.
+
+## Anti-Patterns to Avoid
+
+### Anti-Pattern 1
+What not to do and why.
+
+### Anti-Pattern 2
+What not to do and why.
+
+## Tools and Resources
+
+### Recommended Tools
+- Tool 1: Purpose
+- Tool 2: Purpose
+- Tool 3: Purpose
+
+### Further Reading
+- Resource 1
+- Resource 2
+- Resource 3
+
+## Conclusion
+
+Key takeaways for using this reference guide effectively.

package/docs/skill-candidates/v0.0.11/senior-fullstack/references/development_workflows.md

@@ -0,0 +1,103 @@
+# Development Workflows
+
+## Overview
+
+This reference guide provides comprehensive information for senior fullstack.
+
+## Patterns and Practices
+
+### Pattern 1: Best Practice Implementation
+
+**Description:**
+Detailed explanation of the pattern.
+
+**When to Use:**
+- Scenario 1
+- Scenario 2
+- Scenario 3
+
+**Implementation:**
+```typescript
+// Example code implementation
+export class Example {
+  // Implementation details
+}
+```
+
+**Benefits:**
+- Benefit 1
+- Benefit 2
+- Benefit 3
+
+**Trade-offs:**
+- Consider 1
+- Consider 2
+- Consider 3
+
+### Pattern 2: Advanced Technique
+
+**Description:**
+Another important pattern for senior fullstack.
+
+**Implementation:**
+```typescript
+// Advanced example
+async function advancedExample() {
+  // Code here
+}
+```
+
+## Guidelines
+
+### Code Organization
+- Clear structure
+- Logical separation
+- Consistent naming
+- Proper documentation
+
+### Performance Considerations
+- Optimization strategies
+- Bottleneck identification
+- Monitoring approaches
+- Scaling techniques
+
+### Security Best Practices
+- Input validation
+- Authentication
+- Authorization
+- Data protection
+
+## Common Patterns
+
+### Pattern A
+Implementation details and examples.
+
+### Pattern B
+Implementation details and examples.
+
+### Pattern C
+Implementation details and examples.
+
+## Anti-Patterns to Avoid
+
+### Anti-Pattern 1
+What not to do and why.
+
+### Anti-Pattern 2
+What not to do and why.
+
+## Tools and Resources
+
+### Recommended Tools
+- Tool 1: Purpose
+- Tool 2: Purpose
+- Tool 3: Purpose
+
+### Further Reading
+- Resource 1
+- Resource 2
+- Resource 3
+
+## Conclusion
+
+Key takeaways for using this reference guide effectively.

package/docs/skill-candidates/v0.0.11/senior-fullstack/references/tech_stack_guide.md

@@ -0,0 +1,103 @@
+# Tech Stack Guide
+
+## Overview
+
+This reference guide provides comprehensive information for senior fullstack.
+
+## Patterns and Practices
+
+### Pattern 1: Best Practice Implementation
+
+**Description:**
+Detailed explanation of the pattern.
+
+**When to Use:**
+- Scenario 1
+- Scenario 2
+- Scenario 3
+
+**Implementation:**
+```typescript
+// Example code implementation
+export class Example {
+  // Implementation details
+}
+```
+
+**Benefits:**
+- Benefit 1
+- Benefit 2
+- Benefit 3
+
+**Trade-offs:**
+- Consider 1
+- Consider 2
+- Consider 3
+
+### Pattern 2: Advanced Technique
+
+**Description:**
+Another important pattern for senior fullstack.
+
+**Implementation:**
+```typescript
+// Advanced example
+async function advancedExample() {
+  // Code here
+}
+```
+
+## Guidelines
+
+### Code Organization
+- Clear structure
+- Logical separation
+- Consistent naming
+- Proper documentation
+
+### Performance Considerations
+- Optimization strategies
+- Bottleneck identification
+- Monitoring approaches
+- Scaling techniques
+
+### Security Best Practices
+- Input validation
+- Authentication
+- Authorization
+- Data protection
+
+## Common Patterns
+
+### Pattern A
+Implementation details and examples.
+
+### Pattern B
+Implementation details and examples.
+
+### Pattern C
+Implementation details and examples.
+
+## Anti-Patterns to Avoid
+
+### Anti-Pattern 1
+What not to do and why.
+
+### Anti-Pattern 2
+What not to do and why.
+
+## Tools and Resources
+
+### Recommended Tools
+- Tool 1: Purpose
+- Tool 2: Purpose
+- Tool 3: Purpose
+
+### Further Reading
+- Resource 1
+- Resource 2
+- Resource 3
+
+## Conclusion
+
+Key takeaways for using this reference guide effectively.