Merge main into add-aws-cost-optimization-skills, resolve conflicts by regenerating catalog (927 skills)
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
58
CATALOG.md
58
CATALOG.md
@@ -2,9 +2,9 @@
|
||||
|
||||
Generated at: 2026-02-08T00:00:00.000Z
|
||||
|
||||
Total skills: 891
|
||||
Total skills: 927
|
||||
|
||||
## architecture (60)
|
||||
## architecture (63)
|
||||
|
||||
| Skill | Description | Tags | Triggers |
|
||||
| --- | --- | --- | --- |
|
||||
@@ -14,6 +14,7 @@ Total skills: 891
|
||||
| `architecture-decision-records` | Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant techn... | architecture, decision, records | architecture, decision, records, write, maintain, adrs, following, technical, documentation, documenting, significant, decisions |
|
||||
| `avalonia-viewmodels-zafiro` | Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI. | avalonia, viewmodels, zafiro | avalonia, viewmodels, zafiro, optimal, viewmodel, wizard, creation, reactiveui |
|
||||
| `bash-linux` | Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems. | bash, linux | bash, linux, terminal, critical, commands, piping, error, handling, scripting, working, macos |
|
||||
| `bash-scripting` | Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing. | bash, scripting | bash, scripting, creating, shell, scripts, defensive, error, handling, testing |
|
||||
| `binary-analysis-patterns` | Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, un... | binary | binary, analysis, including, disassembly, decompilation, control, flow, code, recognition, analyzing, executables, understanding |
|
||||
| `brainstorming` | Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and ... | brainstorming | brainstorming, before, creative, constructive, work, features, architecture, behavior, transforms, vague, ideas, validated |
|
||||
| `browser-extension-builder` | Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, c... | browser, extension, builder | browser, extension, builder, building, extensions, solve, real, problems, chrome, firefox, cross, covers |
|
||||
@@ -44,6 +45,7 @@ Total skills: 891
|
||||
| `hig-patterns` | > | hig | hig |
|
||||
| `i18n-localization` | Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support. | i18n, localization | i18n, localization, internationalization, detecting, hardcoded, strings, managing, translations, locale, files, rtl |
|
||||
| `inngest` | Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, ser... | inngest | inngest, serverless, first, background, jobs, event, driven, durable, execution, without, managing, queues |
|
||||
| `kotlin-coroutines-expert` | Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing. | kotlin, coroutines | kotlin, coroutines, flow, covering, structured, concurrency, error, handling, testing |
|
||||
| `monorepo-architect` | Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project devel... | monorepo | monorepo, architect, architecture, dependency, scale, masters, nx, turborepo, bazel, lerna, efficient, multi |
|
||||
| `multi-agent-patterns` | Master orchestrator, peer-to-peer, and hierarchical multi-agent architectures | multi, agent | multi, agent, orchestrator, peer, hierarchical, architectures |
|
||||
| `nerdzao-elite` | Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation. | nerdzao, elite | nerdzao, elite, senior, software, engineer, 15, product, designer, full, planning, architecture, tdd |
|
||||
@@ -65,6 +67,7 @@ Total skills: 891
|
||||
| `tool-design` | Build tools that agents can use effectively, including architectural reduction patterns | | agents, effectively, including, architectural, reduction |
|
||||
| `unreal-engine-cpp-pro` | Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices. | unreal, engine, cpp | unreal, engine, cpp, pro, development, covering, uobject, hygiene, performance |
|
||||
| `wcag-audit-patterns` | Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fi... | wcag, audit | wcag, audit, conduct, accessibility, audits, automated, testing, manual, verification, remediation, guidance, auditing |
|
||||
| `wordpress-theme-development` | WordPress theme development workflow covering theme architecture, template hierarchy, custom post types, block editor support, and responsive design. | wordpress, theme | wordpress, theme, development, covering, architecture, hierarchy, custom, post, types, block, editor, responsive |
|
||||
| `workflow-orchestration-patterns` | Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism cons... | | orchestration, durable, temporal, distributed, covers, vs, activity, separation, saga, state, determinism, constraints |
|
||||
| `workflow-patterns` | Use this skill when implementing tasks according to Conductor's TDD | | skill, implementing, tasks, according, conductor, tdd |
|
||||
| `zapier-make-patterns` | No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code.... | zapier, make | zapier, make, no, code, automation, democratizes, building, formerly, integromat, let, non, developers |
|
||||
@@ -113,7 +116,7 @@ Total skills: 891
|
||||
| `startup-metrics-framework` | This skill should be used when the user asks about \"key startup | startup, metrics, framework | startup, metrics, framework, skill, should, used, user, asks, about, key |
|
||||
| `whatsapp-automation` | Automate WhatsApp Business tasks via Rube MCP (Composio): send messages, manage templates, upload media, and handle contacts. Always search tools first for c... | whatsapp | whatsapp, automation, automate, business, tasks, via, rube, mcp, composio, send, messages, upload |
|
||||
|
||||
## data-ai (143)
|
||||
## data-ai (151)
|
||||
|
||||
| Skill | Description | Tags | Triggers |
|
||||
| --- | --- | --- | --- |
|
||||
@@ -121,8 +124,10 @@ Total skills: 891
|
||||
| `agent-memory-mcp` | A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions). | agent, memory, mcp | agent, memory, mcp, hybrid, provides, persistent, searchable, knowledge, ai, agents, architecture, decisions |
|
||||
| `agent-tool-builder` | Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently... | agent, builder | agent, builder, how, ai, agents, interact, world, well, designed, difference, between, works |
|
||||
| `agents-v2-py` | Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container imag... | agents, v2, py | agents, v2, py, container, foundry, azure, ai, sdk, imagebasedhostedagentdefinition, creating, hosted, custom |
|
||||
| `ai-agent-development` | AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents. | ai, agent | ai, agent, development, building, autonomous, agents, multi, orchestration, crewai, langgraph, custom |
|
||||
| `ai-agents-architect` | Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build ... | ai, agents | ai, agents, architect, designing, building, autonomous, masters, memory, planning, multi, agent, orchestration |
|
||||
| `ai-engineer` | Build production-ready LLM applications, advanced RAG systems, and | ai | ai, engineer, llm, applications, rag |
|
||||
| `ai-ml` | AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features. | ai, ml | ai, ml, machine, learning, covering, llm, application, development, rag, agent, architecture, pipelines |
|
||||
| `ai-product` | Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integra... | ai, product | ai, product, every, powered, question, whether, ll, right, ship, demo, falls, apart |
|
||||
| `ai-wrapper-product` | Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products t... | ai, wrapper, product | ai, wrapper, product, building, products, wrap, apis, openai, anthropic, etc, people, pay |
|
||||
| `analytics-tracking` | > | analytics, tracking | analytics, tracking |
|
||||
@@ -187,6 +192,8 @@ Total skills: 891
|
||||
| `data-quality-frameworks` | Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation r... | data, quality, frameworks | data, quality, frameworks, validation, great, expectations, dbt, tests, contracts, building, pipelines, implementing |
|
||||
| `data-scientist` | Expert data scientist for advanced analytics, machine learning, and | data, scientist | data, scientist, analytics, machine, learning |
|
||||
| `data-storytelling` | Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating dat... | data, storytelling | data, storytelling, transform, compelling, narratives, visualization, context, persuasive, structure, presenting, analytics, stakeholders |
|
||||
| `data-structure-protocol` | Give agents persistent structural memory of a codebase — navigate dependencies, track public APIs, and understand why connections exist without re-reading th... | data, structure, protocol | data, structure, protocol, give, agents, persistent, structural, memory, codebase, navigate, dependencies, track |
|
||||
| `database` | Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering. | database | database, development, operations, covering, sql, nosql, migrations, optimization, data, engineering |
|
||||
| `database-architect` | Expert database architect specializing in data layer design from | database | database, architect, specializing, data, layer |
|
||||
| `database-design` | Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases. | database | database, principles, decision, making, schema, indexing, orm, selection, serverless, databases |
|
||||
| `database-optimizer` | Expert database optimizer specializing in modern performance | database, optimizer | database, optimizer, specializing, performance |
|
||||
@@ -210,6 +217,9 @@ Total skills: 891
|
||||
| `hybrid-search-implementation` | Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides... | hybrid, search | hybrid, search, combine, vector, keyword, improved, retrieval, implementing, rag, building, engines, neither |
|
||||
| `langchain-architecture` | Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implement... | langchain, architecture | langchain, architecture, llm, applications, framework, agents, memory, integration, building, implementing, ai, creating |
|
||||
| `langgraph` | Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles ... | langgraph | langgraph, grade, framework, building, stateful, multi, actor, ai, applications, covers, graph, construction |
|
||||
| `libreoffice/base` | Database management, forms, reports, and data operations with LibreOffice Base. | libreoffice/base | libreoffice/base, base, database, forms, reports, data, operations, libreoffice |
|
||||
| `libreoffice/calc` | Spreadsheet creation, format conversion (ODS/XLSX/CSV), formulas, data automation with LibreOffice Calc. | libreoffice/calc | libreoffice/calc, calc, spreadsheet, creation, format, conversion, ods, xlsx, csv, formulas, data, automation |
|
||||
| `libreoffice/draw` | Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw. | libreoffice/draw | libreoffice/draw, draw, vector, graphics, diagram, creation, format, conversion, odg, svg, pdf, libreoffice |
|
||||
| `llm-application-dev-ai-assistant` | You are an AI assistant development expert specializing in creating intelligent conversational interfaces, chatbots, and AI-powered applications. Design comp... | llm, application, dev, ai | llm, application, dev, ai, assistant, development, specializing, creating, intelligent, conversational, interfaces, chatbots |
|
||||
| `llm-application-dev-langchain-agent` | You are an expert LangChain agent developer specializing in production-grade AI systems using LangChain 0.1+ and LangGraph. | llm, application, dev, langchain, agent | llm, application, dev, langchain, agent, developer, specializing, grade, ai, langgraph |
|
||||
| `llm-application-dev-prompt-optimize` | You are an expert prompt engineer specializing in crafting effective prompts for LLMs through advanced techniques including constitutional AI, chain-of-thoug... | llm, application, dev, prompt, optimize | llm, application, dev, prompt, optimize, engineer, specializing, crafting, effective, prompts, llms, through |
|
||||
@@ -226,12 +236,13 @@ Total skills: 891
|
||||
| `podcast-generation` | Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, aud... | podcast, generation | podcast, generation, generate, ai, powered, style, audio, narratives, azure, openai, gpt, realtime |
|
||||
| `postgres-best-practices` | Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, o... | postgres, best, practices | postgres, best, practices, performance, optimization, supabase, skill, writing, reviewing, optimizing, queries, schema |
|
||||
| `postgresql` | Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features | postgresql | postgresql, specific, schema, covers, data, types, indexing, constraints, performance, features |
|
||||
| `postgresql-optimization` | PostgreSQL database optimization workflow for query tuning, indexing strategies, performance analysis, and production database management. | postgresql, optimization | postgresql, optimization, database, query, tuning, indexing, performance, analysis |
|
||||
| `prisma-expert` | Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, m... | prisma | prisma, orm, schema, migrations, query, optimization, relations, modeling, database, operations, proactively, issues |
|
||||
| `prompt-caching` | Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) Use when: prompt caching, cache... | prompt, caching | prompt, caching, llm, prompts, including, anthropic, response, cag, cache, augmented, generation, augm |
|
||||
| `prompt-engineering-patterns` | Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, impro... | prompt, engineering | prompt, engineering, techniques, maximize, llm, performance, reliability, controllability, optimizing, prompts, improving, outputs |
|
||||
| `pydantic-models-py` | Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants. Use when defining API request/response schem... | pydantic, models, py | pydantic, models, py, following, multi, model, base, update, response, indb, variants, defining |
|
||||
| `rag-engineer` | Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LL... | rag | rag, engineer, building, retrieval, augmented, generation, masters, embedding, models, vector, databases, chunking |
|
||||
| `rag-implementation` | Build Retrieval-Augmented Generation (RAG) systems for LLM applications with vector databases and semantic search. Use when implementing knowledge-grounded A... | rag | rag, retrieval, augmented, generation, llm, applications, vector, databases, semantic, search, implementing, knowledge |
|
||||
| `rag-implementation` | RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimiza... | rag | rag, retrieval, augmented, generation, covering, embedding, selection, vector, database, setup, chunking, optimization |
|
||||
| `react-ui-patterns` | Modern React UI patterns for loading states, error handling, and data fetching. Use when building UI components, handling async data, or managing UI states. | react, ui | react, ui, loading, states, error, handling, data, fetching, building, components, async, managing |
|
||||
| `segment-cdp` | Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinat... | segment, cdp | segment, cdp, customer, data, platform, including, analytics, js, server, side, tracking, plans |
|
||||
| `sendgrid-automation` | Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Al... | sendgrid | sendgrid, automation, automate, email, operations, including, sending, emails, managing, contacts, lists, sender |
|
||||
@@ -261,13 +272,15 @@ Total skills: 891
|
||||
| `xlsx-official` | Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work ... | xlsx, official | xlsx, official, spreadsheet, creation, editing, analysis, formulas, formatting, data, visualization, claude, work |
|
||||
| `youtube-automation` | Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools firs... | youtube | youtube, automation, automate, tasks, via, rube, mcp, composio, upload, videos, playlists, search |
|
||||
|
||||
## development (141)
|
||||
## development (148)
|
||||
|
||||
| Skill | Description | Tags | Triggers |
|
||||
| --- | --- | --- | --- |
|
||||
| `3d-web-experience` | Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portf... | 3d, web, experience | 3d, web, experience, building, experiences, three, js, react, fiber, spline, webgl, interactive |
|
||||
| `algolia-search` | Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instan... | algolia, search | algolia, search, indexing, react, instantsearch, relevance, tuning, adding, api, functionality |
|
||||
| `android-jetpack-compose-expert` | Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3. | android, jetpack, compose | android, jetpack, compose, guidance, building, uis, covering, state, navigation, performance, material |
|
||||
| `api-design-principles` | Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, revie... | api, principles | api, principles, rest, graphql, intuitive, scalable, maintainable, apis, delight, developers, designing, new |
|
||||
| `api-documentation` | API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation. | api, documentation | api, documentation, generating, openapi, specs, creating, developer, guides, maintaining |
|
||||
| `api-documentation-generator` | Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices | api, documentation, generator | api, documentation, generator, generate, developer, friendly, code, including, endpoints, parameters, examples |
|
||||
| `api-patterns` | API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination. | api | api, principles, decision, making, rest, vs, graphql, trpc, selection, response, formats, versioning |
|
||||
| `app-store-optimization` | Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store | app, store, optimization | app, store, optimization, complete, aso, toolkit, researching, optimizing, tracking, mobile, performance, apple |
|
||||
@@ -317,6 +330,7 @@ Total skills: 891
|
||||
| `azure-web-pubsub-ts` | Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSoc... | azure, web, pubsub, ts | azure, web, pubsub, ts, real, time, messaging, applications, sdks, javascript, client, implementing |
|
||||
| `backend-architect` | Expert backend architect specializing in scalable API design, | backend | backend, architect, specializing, scalable, api |
|
||||
| `backend-dev-guidelines` | Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency i... | backend, dev, guidelines | backend, dev, guidelines, opinionated, development, standards, node, js, express, typescript, microservices, covers |
|
||||
| `bevy-ecs-expert` | Master Bevy's Entity Component System (ECS) in Rust, covering Systems, Queries, Resources, and parallel scheduling. | bevy, ecs | bevy, ecs, entity, component, rust, covering, queries, resources, parallel, scheduling |
|
||||
| `bullmq-specialist` | BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull que... | bullmq | bullmq, redis, backed, job, queues, background, processing, reliable, async, execution, node, js |
|
||||
| `bun-development` | Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bu... | bun | bun, development, javascript, typescript, runtime, covers, package, bundling, testing, migration, node, js |
|
||||
| `cc-skill-coding-standards` | Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development. | cc, skill, coding, standards | cc, skill, coding, standards, universal, typescript, javascript, react, node, js, development |
|
||||
@@ -327,8 +341,10 @@ Total skills: 891
|
||||
| `dbos-golang` | DBOS Go SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Go code with DBOS, creating workflows and ... | dbos, golang | dbos, golang, go, sdk, building, reliable, fault, tolerant, applications, durable, skill, writing |
|
||||
| `dbos-python` | DBOS Python SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Python code with DBOS, creating workfl... | dbos, python | dbos, python, sdk, building, reliable, fault, tolerant, applications, durable, skill, writing, code |
|
||||
| `dbos-typescript` | DBOS TypeScript SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing TypeScript code with DBOS, creatin... | dbos, typescript | dbos, typescript, sdk, building, reliable, fault, tolerant, applications, durable, skill, writing, code |
|
||||
| `development` | Comprehensive web, mobile, and backend development workflow bundling frontend, backend, full-stack, and mobile development skills for end-to-end application ... | | development, web, mobile, backend, bundling, frontend, full, stack, skills, application, delivery |
|
||||
| `discord-bot-architect` | Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactiv... | discord, bot | discord, bot, architect, specialized, skill, building, bots, covers, js, javascript, pycord, python |
|
||||
| `django-pro` | Master Django 5.x with async views, DRF, Celery, and Django | django | django, pro, async, views, drf, celery |
|
||||
| `documentation` | Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing. | documentation | documentation, generation, covering, api, docs, architecture, readme, files, code, comments, technical, writing |
|
||||
| `dotnet-architect` | Expert .NET backend architect specializing in C#, ASP.NET Core, | dotnet | dotnet, architect, net, backend, specializing, asp, core |
|
||||
| `dotnet-backend-patterns` | Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Ent... | dotnet, backend | dotnet, backend, net, development, building, robust, apis, mcp, servers, enterprise, applications, covers |
|
||||
| `exa-search` | Semantic search, similar content discovery, and structured research using Exa API | exa, search | exa, search, semantic, similar, content, discovery, structured, research, api |
|
||||
@@ -370,6 +386,7 @@ Total skills: 891
|
||||
| `observe-whatsapp` | Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when in... | observe, whatsapp | observe, whatsapp, troubleshoot, kapso, debug, message, delivery, inspect, webhook, deliveries, retries, triage |
|
||||
| `product-manager-toolkit` | Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market ... | product, manager | product, manager, toolkit, managers, including, rice, prioritization, customer, interview, analysis, prd, discovery |
|
||||
| `python-development-python-scaffold` | You are a Python project architecture expert specializing in scaffolding production-ready Python applications. Generate complete project structures with mode... | python | python, development, scaffold, architecture, specializing, scaffolding, applications, generate, complete, structures, tooling, uv |
|
||||
| `python-fastapi-development` | Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns. | python, fastapi | python, fastapi, development, backend, async, sqlalchemy, pydantic, authentication, api |
|
||||
| `python-packaging` | Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, cre... | python, packaging | python, packaging, distributable, packages, proper, structure, setup, py, pyproject, toml, publishing, pypi |
|
||||
| `python-patterns` | Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying. | python | python, development, principles, decision, making, framework, selection, async, type, hints, structure, teaches |
|
||||
| `python-performance-optimization` | Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottleneck... | python, performance, optimization | python, performance, optimization, profile, optimize, code, cprofile, memory, profilers, debugging, slow, optimizing |
|
||||
@@ -380,6 +397,7 @@ Total skills: 891
|
||||
| `react-flow-node-ts` | Create React Flow node components with TypeScript types, handles, and Zustand integration. Use when building custom nodes for React Flow canvas, creating vis... | react, flow, node, ts | react, flow, node, ts, components, typescript, types, zustand, integration, building, custom, nodes |
|
||||
| `react-modernization` | Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, m... | react, modernization | react, modernization, upgrade, applications, latest, versions, migrate, class, components, hooks, adopt, concurrent |
|
||||
| `react-native-architecture` | Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, impleme... | react, native, architecture | react, native, architecture, apps, expo, navigation, modules, offline, sync, cross, platform, developing |
|
||||
| `react-nextjs-development` | React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns. | react, nextjs | react, nextjs, development, next, js, 14, application, app, router, server, components, typescript |
|
||||
| `react-patterns` | Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices. | react | react, principles, hooks, composition, performance, typescript |
|
||||
| `react-state-management` | Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosin... | react, state | react, state, redux, toolkit, zustand, jotai, query, setting, up, global, managing, server |
|
||||
| `reference-builder` | Creates exhaustive technical references and API documentation. | reference, builder | reference, builder, creates, exhaustive, technical, references, api, documentation |
|
||||
@@ -407,7 +425,7 @@ Total skills: 891
|
||||
| `webapp-testing` | Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing... | webapp | webapp, testing, toolkit, interacting, local, web, applications, playwright, supports, verifying, frontend, functionality |
|
||||
| `zustand-store-ts` | Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creati... | zustand, store, ts | zustand, store, ts, stores, typescript, subscribewithselector, middleware, proper, state, action, separation, building |
|
||||
|
||||
## general (216)
|
||||
## general (218)
|
||||
|
||||
| Skill | Description | Tags | Triggers |
|
||||
| --- | --- | --- | --- |
|
||||
@@ -525,6 +543,7 @@ Total skills: 891
|
||||
| `git-pr-workflows-pr-enhance` | You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descri... | git, pr, enhance | git, pr, enhance, optimization, specializing, creating, high, quality, pull, requests, facilitate, efficient |
|
||||
| `git-pushing` | Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to... | git, pushing | git, pushing, stage, commit, push, changes, conventional, messages, user, wants, mentions, remote |
|
||||
| `github-issue-creator` | Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error me... | github, issue, creator | github, issue, creator, convert, raw, notes, error, logs, voice, dictation, screenshots, crisp |
|
||||
| `godot-4-migration` | Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports. | godot, 4, migration | godot, 4, migration, specialized, migrating, gdscript, covering, syntax, changes, tweens, exports |
|
||||
| `graphql-architect` | Master modern GraphQL with federation, performance optimization, | graphql | graphql, architect, federation, performance, optimization |
|
||||
| `hig-components-content` | > | hig, components, content | hig, components, content |
|
||||
| `hig-components-controls` | >- | hig, components, controls | hig, components, controls |
|
||||
@@ -594,6 +613,7 @@ Total skills: 891
|
||||
| `scala-pro` | Master enterprise-grade Scala development with functional | scala | scala, pro, enterprise, grade, development, functional |
|
||||
| `schema-markup` | > | schema, markup | schema, markup |
|
||||
| `search-specialist` | Expert web researcher using advanced search techniques and synthesis. Masters search operators, result filtering, and multi-source verification. Handles comp... | search | search, web, researcher, techniques, synthesis, masters, operators, result, filtering, multi, source, verification |
|
||||
| `shader-programming-glsl` | Expert guide for writing efficient GLSL shaders (Vertex/Fragment) for web and game engines, covering syntax, uniforms, and common effects. | shader, programming, glsl | shader, programming, glsl, writing, efficient, shaders, vertex, fragment, web, game, engines, covering |
|
||||
| `sharp-edges` | Identify error-prone APIs and dangerous configurations | sharp, edges | sharp, edges, identify, error, prone, apis, dangerous, configurations |
|
||||
| `shellcheck-configuration` | Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuri... | shellcheck, configuration | shellcheck, configuration, static, analysis, usage, shell, script, quality, setting, up, linting, infrastructure |
|
||||
| `shodan-reconnaissance` | This skill should be used when the user asks to "search for exposed devices on the internet," "perform Shodan reconnaissance," "find vulnerable services usin... | shodan, reconnaissance | shodan, reconnaissance, skill, should, used, user, asks, search, exposed, devices, internet, perform |
|
||||
@@ -628,7 +648,7 @@ Total skills: 891
|
||||
| `x-article-publisher-skill` | Publish articles to X/Twitter | x, article, publisher, skill | x, article, publisher, skill, publish, articles, twitter |
|
||||
| `youtube-summarizer` | Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks | video, summarization, transcription, youtube, content-analysis | video, summarization, transcription, youtube, content-analysis, summarizer, extract, transcripts, videos, generate, detailed, summaries |
|
||||
|
||||
## infrastructure (85)
|
||||
## infrastructure (90)
|
||||
|
||||
| Skill | Description | Tags | Triggers |
|
||||
| --- | --- | --- | --- |
|
||||
@@ -653,6 +673,7 @@ Total skills: 891
|
||||
| `cicd-automation-workflow-automate` | You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Desig... | cicd, automate | cicd, automate, automation, specializing, creating, efficient, ci, cd, pipelines, github, actions, automated |
|
||||
| `claude-d3js-skill` | Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisati... | claude, d3js, skill | claude, d3js, skill, creating, interactive, data, visualisations, d3, js, should, used, custom |
|
||||
| `cloud-architect` | Expert cloud architect specializing in AWS/Azure/GCP multi-cloud | cloud | cloud, architect, specializing, aws, azure, gcp, multi |
|
||||
| `cloud-devops` | Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development. | cloud, devops | cloud, devops, infrastructure, covering, aws, azure, gcp, kubernetes, terraform, ci, cd, monitoring |
|
||||
| `code-review-ai-ai-review` | You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Levera... | code, ai | code, ai, review, powered, combining, automated, static, analysis, intelligent, recognition, devops, leverage |
|
||||
| `cost-optimization` | Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing... | cost, optimization | cost, optimization, optimize, cloud, costs, through, resource, rightsizing, tagging, reserved, instances, spending |
|
||||
| `data-engineering-data-pipeline` | You are a data pipeline architecture expert specializing in scalable, reliable, and cost-effective data pipelines for batch and streaming data processing. | data, engineering, pipeline | data, engineering, pipeline, architecture, specializing, scalable, reliable, cost, effective, pipelines, batch, streaming |
|
||||
@@ -664,6 +685,7 @@ Total skills: 891
|
||||
| `deployment-validation-config-validate` | You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensi... | deployment, validation, config, validate | deployment, validation, config, validate, configuration, specializing, validating, testing, ensuring, correctness, application, configurations |
|
||||
| `distributed-debugging-debug-trace` | You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging wo... | distributed, debugging, debug, trace | distributed, debugging, debug, trace, specializing, setting, up, environments, tracing, diagnostic, configure, solutions |
|
||||
| `distributed-tracing` | Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microserv... | distributed, tracing | distributed, tracing, jaeger, tempo, track, requests, microservices, identify, performance, bottlenecks, debugging, analyzing |
|
||||
| `e2e-testing` | End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration. | e2e | e2e, testing, playwright, browser, automation, visual, regression, cross, ci, cd, integration |
|
||||
| `e2e-testing-patterns` | Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when... | e2e | e2e, testing, playwright, cypress, reliable, test, suites, catch, bugs, improve, confidence, enable |
|
||||
| `error-debugging-error-analysis` | You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehens... | error, debugging | error, debugging, analysis, deep, expertise, distributed, analyzing, incidents, implementing, observability, solutions |
|
||||
| `error-debugging-error-trace` | You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, conf... | error, debugging, trace | error, debugging, trace, tracking, observability, specializing, implementing, monitoring, solutions, set, up, configure |
|
||||
@@ -688,7 +710,9 @@ Total skills: 891
|
||||
| `iterate-pr` | Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automa... | iterate, pr | iterate, pr, until, ci, passes, fix, failures, address, review, feedback, continuously, push |
|
||||
| `kpi-dashboard-design` | Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboard... | kpi, dashboard | kpi, dashboard, effective, dashboards, metrics, selection, visualization, real, time, monitoring, building, business |
|
||||
| `kubernetes-architect` | Expert Kubernetes architect specializing in cloud-native | kubernetes | kubernetes, architect, specializing, cloud, native |
|
||||
| `kubernetes-deployment` | Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations. | kubernetes, deployment | kubernetes, deployment, container, orchestration, helm, charts, mesh, k8s, configurations |
|
||||
| `langfuse` | Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, Lla... | langfuse | langfuse, open, source, llm, observability, platform, covers, tracing, prompt, evaluation, datasets, integration |
|
||||
| `linux-troubleshooting` | Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures. | linux, troubleshooting | linux, troubleshooting, diagnosing, resolving, issues, performance, problems, failures |
|
||||
| `llm-app-patterns` | Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI... | llm, app | llm, app, building, applications, covers, rag, pipelines, agent, architectures, prompt, ides, llmops |
|
||||
| `machine-learning-ops-ml-pipeline` | Design and implement a complete ML pipeline for: $ARGUMENTS | machine, learning, ops, ml, pipeline | machine, learning, ops, ml, pipeline, complete, arguments |
|
||||
| `manifest` | Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin. | manifest | manifest, install, configure, observability, plugin, agents, setting, up, telemetry, configuring, api, keys |
|
||||
@@ -710,6 +734,7 @@ Total skills: 891
|
||||
| `service-mesh-observability` | Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debu... | service, mesh, observability | service, mesh, observability, meshes, including, distributed, tracing, metrics, visualization, setting, up, monitoring |
|
||||
| `slo-implementation` | Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability t... | slo | slo, define, level, indicators, slis, objectives, slos, error, budgets, alerting, establishing, reliability |
|
||||
| `sql-pro` | Master modern SQL with cloud-native databases, OLTP/OLAP | sql | sql, pro, cloud, native, databases, oltp, olap |
|
||||
| `terraform-infrastructure` | Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale. | terraform, infrastructure | terraform, infrastructure, code, provisioning, cloud, resources, creating, reusable, modules, managing, scale |
|
||||
| `terraform-module-library` | Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure mod... | terraform, module, library | terraform, module, library, reusable, modules, aws, azure, gcp, infrastructure, following, code, creating |
|
||||
| `terraform-skill` | Terraform infrastructure as code best practices | terraform, skill | terraform, skill, infrastructure, code |
|
||||
| `terraform-specialist` | Expert Terraform/OpenTofu specialist mastering advanced IaC | terraform | terraform, opentofu, mastering, iac |
|
||||
@@ -718,7 +743,7 @@ Total skills: 891
|
||||
| `wireshark-analysis` | This skill should be used when the user asks to "analyze network traffic with Wireshark", "capture packets for troubleshooting", "filter PCAP files", "follow... | wireshark | wireshark, analysis, skill, should, used, user, asks, analyze, network, traffic, capture, packets |
|
||||
| `workflow-automation` | Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost... | | automation, infrastructure, makes, ai, agents, reliable, without, durable, execution, network, hiccup, during |
|
||||
|
||||
## security (95)
|
||||
## security (100)
|
||||
|
||||
| Skill | Description | Tags | Triggers |
|
||||
| --- | --- | --- | --- |
|
||||
@@ -728,6 +753,7 @@ Total skills: 891
|
||||
| `antigravity-workflows` | Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA. | antigravity | antigravity, orchestrate, multiple, skills, through, guided, saas, mvp, delivery, security, audits, ai |
|
||||
| `api-fuzzing-bug-bounty` | This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetrat... | api, fuzzing, bug, bounty | api, fuzzing, bug, bounty, skill, should, used, user, asks, test, security, fuzz |
|
||||
| `api-security-best-practices` | Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities | api, security, best, practices | api, security, best, practices, secure, including, authentication, authorization, input, validation, rate, limiting |
|
||||
| `api-security-testing` | API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices. | api, security | api, security, testing, rest, graphql, apis, covering, authentication, authorization, rate, limiting, input |
|
||||
| `attack-tree-construction` | Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to s... | attack, tree, construction | attack, tree, construction, trees, visualize, threat, paths, mapping, scenarios, identifying, defense, gaps |
|
||||
| `auth-implementation-patterns` | Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use wh... | auth | auth, authentication, authorization, including, jwt, oauth2, session, rbac, secure, scalable, access, control |
|
||||
| `aws-penetration-testing` | This skill should be used when the user asks to "pentest AWS", "test AWS security", "enumerate IAM", "exploit cloud infrastructure", "AWS privilege escalatio... | aws, penetration | aws, penetration, testing, skill, should, used, user, asks, pentest, test, security, enumerate |
|
||||
@@ -747,7 +773,7 @@ Total skills: 891
|
||||
| `code-reviewer` | Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Mas... | code | code, reviewer, elite, review, specializing, ai, powered, analysis, security, vulnerabilities, performance, optimization |
|
||||
| `codebase-cleanup-deps-audit` | You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for ... | codebase, cleanup, deps, audit | codebase, cleanup, deps, audit, dependency, security, specializing, vulnerability, scanning, license, compliance, supply |
|
||||
| `database-migration` | Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databas... | database, migration | database, migration, execute, migrations, orms, platforms, zero, downtime, data, transformation, rollback, procedures |
|
||||
| `database-migrations-sql-migrations` | SQL database migrations with zero-downtime strategies for | database, sql, migrations, postgresql, mysql, flyway, liquibase, alembic, zero-downtime | database, sql, migrations, postgresql, mysql, flyway, liquibase, alembic, zero-downtime, zero, downtime |
|
||||
| `database-migrations-sql-migrations` | SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans. | database, migrations, sql | database, migrations, sql, zero, downtime, postgresql, mysql, server, data, integrity, rollback, plans |
|
||||
| `dependency-management-deps-audit` | You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for ... | dependency, deps, audit | dependency, deps, audit, security, specializing, vulnerability, scanning, license, compliance, supply, chain, analyze |
|
||||
| `deployment-pipeline-design` | Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up... | deployment, pipeline | deployment, pipeline, multi, stage, ci, cd, pipelines, approval, gates, security, checks, orchestration |
|
||||
| `design-orchestration` | Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order. Prevents premature imp... | | orchestration, orchestrates, routing, work, through, brainstorming, multi, agent, review, execution, readiness, correct |
|
||||
@@ -794,6 +820,7 @@ Total skills: 891
|
||||
| `sast-configuration` | Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, ... | sast, configuration | sast, configuration, configure, static, application, security, testing, automated, vulnerability, detection, code, setting |
|
||||
| `scanning-tools` | This skill should be used when the user asks to "perform vulnerability scanning", "scan networks for open ports", "assess web application security", "scan wi... | scanning | scanning, skill, should, used, user, asks, perform, vulnerability, scan, networks, open, ports |
|
||||
| `secrets-management` | Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentia... | secrets | secrets, secure, ci, cd, pipelines, vault, aws, manager, native, platform, solutions, handling |
|
||||
| `security-audit` | Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening. | security, audit | security, audit, auditing, covering, web, application, testing, api, penetration, vulnerability, scanning, hardening |
|
||||
| `security-auditor` | Expert security auditor specializing in DevSecOps, comprehensive | security, auditor | security, auditor, specializing, devsecops |
|
||||
| `security-bluebook-builder` | Build security Blue Books for sensitive apps | security, bluebook, builder | security, bluebook, builder, blue, books, sensitive, apps |
|
||||
| `security-compliance-compliance-check` | You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. ... | security, compliance, check | security, compliance, check, specializing, regulatory, requirements, software, including, gdpr, hipaa, soc2, pci |
|
||||
@@ -815,10 +842,13 @@ Total skills: 891
|
||||
| `varlock-claude-skill` | Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits | varlock, claude, skill | varlock, claude, skill, secure, environment, variable, ensuring, secrets, never, exposed, sessions, terminals |
|
||||
| `vulnerability-scanner` | Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization. | vulnerability, scanner | vulnerability, scanner, analysis, principles, owasp, 2025, supply, chain, security, attack, surface, mapping |
|
||||
| `web-design-guidelines` | Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"ch... | web, guidelines | web, guidelines, review, ui, code, interface, compliance, asked, my, check, accessibility, audit |
|
||||
| `web-security-testing` | Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues. | web, security | web, security, testing, application, owasp, top, 10, vulnerabilities, including, injection, xss, authentication |
|
||||
| `wiki-onboarding` | Generates two complementary onboarding guides — a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants... | wiki, onboarding | wiki, onboarding, generates, two, complementary, guides, principal, level, architectural, deep, dive, zero |
|
||||
| `wiki-researcher` | Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-dept... | wiki, researcher | wiki, researcher, conducts, multi, turn, iterative, deep, research, specific, topics, within, codebase |
|
||||
| `wordpress` | Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening. | wordpress | wordpress, complete, development, covering, theme, plugin, creation, woocommerce, integration, performance, optimization, security |
|
||||
| `wordpress-plugin-development` | WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, and security best practices. | wordpress, plugin | wordpress, plugin, development, covering, architecture, hooks, admin, interfaces, rest, api, security |
|
||||
|
||||
## testing (31)
|
||||
## testing (32)
|
||||
|
||||
| Skill | Description | Tags | Triggers |
|
||||
| --- | --- | --- | --- |
|
||||
@@ -847,6 +877,7 @@ Total skills: 891
|
||||
| `tdd-workflows-tdd-refactor` | Use when working with tdd workflows tdd refactor | tdd, refactor | tdd, refactor, working |
|
||||
| `test-driven-development` | Use when implementing any feature or bugfix, before writing implementation code | driven | driven, test, development, implementing, any, feature, bugfix, before, writing, code |
|
||||
| `test-fixing` | Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test sui... | fixing | fixing, test, run, tests, systematically, fix, all, failing, smart, error, grouping, user |
|
||||
| `testing-qa` | Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance. | qa | qa, testing, covering, unit, integration, e2e, browser, automation, quality, assurance |
|
||||
| `ui-visual-validator` | Rigorous visual validation expert specializing in UI testing, | ui, visual, validator | ui, visual, validator, rigorous, validation, specializing, testing |
|
||||
| `unit-testing-test-generate` | Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus. | unit, generate | unit, generate, testing, test, maintainable, tests, languages, strong, coverage, edge, case |
|
||||
| `web3-testing` | Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, ... | web3 | web3, testing, test, smart, contracts, comprehensively, hardhat, foundry, unit, tests, integration, mainnet |
|
||||
@@ -854,7 +885,7 @@ Total skills: 891
|
||||
| `wordpress-penetration-testing` | This skill should be used when the user asks to "pentest WordPress sites", "scan WordPress for vulnerabilities", "enumerate WordPress users, themes, or plugi... | wordpress, penetration | wordpress, penetration, testing, skill, should, used, user, asks, pentest, sites, scan, vulnerabilities |
|
||||
| `xss-html-injection` | This skill should be used when the user asks to "test for XSS vulnerabilities", "perform cross-site scripting attacks", "identify HTML injection flaws", "exp... | xss, html, injection | xss, html, injection, skill, should, used, user, asks, test, vulnerabilities, perform, cross |
|
||||
|
||||
## workflow (81)
|
||||
## workflow (86)
|
||||
|
||||
| Skill | Description | Tags | Triggers |
|
||||
| --- | --- | --- | --- |
|
||||
@@ -902,6 +933,8 @@ Total skills: 891
|
||||
| `jira-automation` | Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas. | jira | jira, automation, automate, tasks, via, rube, mcp, composio, issues, sprints, boards, comments |
|
||||
| `kaizen` | Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss proce... | kaizen | kaizen, continuous, improvement, error, proofing, standardization, skill, user, wants, improve, code, quality |
|
||||
| `klaviyo-automation` | Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools... | klaviyo | klaviyo, automation, automate, tasks, via, rube, mcp, composio, email, sms, campaigns, inspect |
|
||||
| `libreoffice/impress` | Presentation creation, format conversion (ODP/PPTX/PDF), slide automation with LibreOffice Impress. | libreoffice/impress | libreoffice/impress, impress, presentation, creation, format, conversion, odp, pptx, pdf, slide, automation, libreoffice |
|
||||
| `libreoffice/writer` | Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer. | libreoffice/writer | libreoffice/writer, writer, document, creation, format, conversion, odt, docx, pdf, mail, merge, automation |
|
||||
| `linear-automation` | Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas. | linear | linear, automation, automate, tasks, via, rube, mcp, composio, issues, cycles, teams, labels |
|
||||
| `linkedin-automation` | Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for curre... | linkedin | linkedin, automation, automate, tasks, via, rube, mcp, composio, posts, profile, company, info |
|
||||
| `make-automation` | Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas. | make | make, automation, automate, integromat, tasks, via, rube, mcp, composio, operations, enums, language |
|
||||
@@ -911,7 +944,9 @@ Total skills: 891
|
||||
| `monday-automation` | Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for cu... | monday | monday, automation, automate, com, work, including, boards, items, columns, groups, subitems, updates |
|
||||
| `nerdzao-elite-gemini-high` | Modo Elite Coder + UX Pixel-Perfect otimizado especificamente para Gemini 3.1 Pro High. Workflow completo com foco em qualidade máxima e eficiência de tokens. | nerdzao, elite, gemini, high | nerdzao, elite, gemini, high, modo, coder, ux, pixel, perfect, otimizado, especificamente, para |
|
||||
| `notion-automation` | Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas. | notion | notion, automation, automate, tasks, via, rube, mcp, composio, pages, databases, blocks, comments |
|
||||
| `office-productivity` | Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Offi... | office, productivity | office, productivity, covering, document, creation, spreadsheet, automation, presentation, generation, integration, libreoffice, microsoft |
|
||||
| `one-drive-automation` | Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first... | one, drive | one, drive, automation, automate, onedrive, file, search, uploads, downloads, sharing, permissions, folder |
|
||||
| `os-scripting` | Operating system and shell scripting troubleshooting workflow for Linux, macOS, and Windows. Covers bash scripting, system administration, debugging, and aut... | os, scripting | os, scripting, operating, shell, troubleshooting, linux, macos, windows, covers, bash, administration, debugging |
|
||||
| `outlook-automation` | Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas. | outlook | outlook, automation, automate, tasks, via, rube, mcp, composio, emails, calendar, contacts, folders |
|
||||
| `outlook-calendar-automation` | Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools fir... | outlook, calendar | outlook, calendar, automation, automate, tasks, via, rube, mcp, composio, events, attendees, find |
|
||||
| `pagerduty-automation` | Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools firs... | pagerduty | pagerduty, automation, automate, tasks, via, rube, mcp, composio, incidents, schedules, escalation, policies |
|
||||
@@ -935,6 +970,7 @@ Total skills: 891
|
||||
| `twitter-automation` | Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas. | twitter | twitter, automation, automate, tasks, via, rube, mcp, composio, posts, search, users, bookmarks |
|
||||
| `vercel-automation` | Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas. | vercel | vercel, automation, automate, tasks, via, rube, mcp, composio, deployments, domains, dns, env |
|
||||
| `webflow-automation` | Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first fo... | webflow | webflow, automation, automate, cms, collections, site, publishing, page, asset, uploads, ecommerce, orders |
|
||||
| `wordpress-woocommerce-development` | WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization. | wordpress, woocommerce | wordpress, woocommerce, development, store, covering, setup, payment, integration, shipping, configuration, customization |
|
||||
| `wrike-automation` | Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first ... | wrike | wrike, automation, automate, via, rube, mcp, composio, tasks, folders, assign, work, track |
|
||||
| `zendesk-automation` | Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas. | zendesk | zendesk, automation, automate, tasks, via, rube, mcp, composio, tickets, users, organizations, replies |
|
||||
| `zoho-crm-automation` | Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for curre... | zoho, crm | zoho, crm, automation, automate, tasks, via, rube, mcp, composio, update, records, search |
|
||||
|
||||
33
CHANGELOG.md
33
CHANGELOG.md
@@ -7,6 +7,39 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
|
||||
---
|
||||
|
||||
## [6.1.0] - 2026-02-23 - "Issues Fix & Community Expansion"
|
||||
|
||||
> **Bugfixes for #116 and #120, plus Game Dev bundle, Android skills, Workflow Bundles, LibreOffice, Data Structure Protocol, and Kiro IDE support.**
|
||||
|
||||
This release fixes the YAML syntax error in database-migrations-sql-migrations (issue #116), adds a typo alias so `shopify—development` (em dash) resolves to `shopify-development` (issue #120), and ships a large set of community PRs: Game Development Expansion (Bevy ECS, GLSL, Godot 4), Android Modern Development (Compose + Coroutines), Workflow Bundles and LibreOffice skills, Data Structure Protocol, and Kiro CLI/IDE support.
|
||||
|
||||
## New Skills
|
||||
|
||||
- **Game Development Expansion** (PR #121): `bevy-ecs-expert`, `shader-programming-glsl`, `godot-4-migration`.
|
||||
- **Android Modern Development** (PR #118): `android-jetpack-compose-expert`, `kotlin-coroutines-expert`.
|
||||
- **Workflow Bundles & LibreOffice** (PR #113): Workflow bundles readme, LibreOffice skills (Base, Calc, Draw, Impress, Writer), plus office-productivity, WordPress suite, and many domain skills (ai-agent-development, cloud-devops, database, e2e-testing, security-audit, terraform-infrastructure, etc.).
|
||||
- **Data Structure Protocol** (PR #114): `data-structure-protocol`.
|
||||
- **Kiro CLI and Kiro IDE** (PR #122): Documentation and support for Kiro.
|
||||
|
||||
## Improvements
|
||||
|
||||
- **YAML fix** (PR #119, fixes #116): Resolved invalid YAML in `database-migrations-sql-migrations/SKILL.md` (description block mapping); removed non-standard frontmatter and standardized section headers.
|
||||
- **Skill matching** (fixes #120): Added typo alias `shopify—development` → `shopify-development` so em-dash input resolves correctly.
|
||||
- **Registry**: Now tracking 925 skills.
|
||||
|
||||
## Credits
|
||||
|
||||
- **@nikolasdehor** for YAML fix (PR #119), Game Development Expansion (PR #121), Android Modern Development (PR #118)
|
||||
- **@ssumanbiswas** for Kiro CLI and Kiro IDE support (PR #122)
|
||||
- **@munir-abbasi** for Workflow Bundles and LibreOffice Skills (PR #113)
|
||||
- **@k-kolomeitsev** for Data Structure Protocol (PR #114)
|
||||
|
||||
---
|
||||
|
||||
_Upgrade now: `git pull origin main` to fetch the latest skills._
|
||||
|
||||
---
|
||||
|
||||
## [6.0.0] - 2026-02-22 - "Codex YAML Fix & Community PRs"
|
||||
|
||||
> **Major release: Codex frontmatter fixes, AWS Security & Compliance skills, Antigravity Workspace Manager CLI, and validation fixes.**
|
||||
|
||||
59
README.md
59
README.md
@@ -1,12 +1,12 @@
|
||||
# 🌌 Antigravity Awesome Skills: 891+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
|
||||
# 🌌 Antigravity Awesome Skills: 927+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
|
||||
|
||||
> **The Ultimate Collection of 891+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode, AdaL**
|
||||
> **The Ultimate Collection of 927+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode, AdaL**
|
||||
|
||||
[](https://opensource.org/licenses/MIT)
|
||||
[](https://claude.ai)
|
||||
[](https://github.com/google-gemini/gemini-cli)
|
||||
[](https://github.com/openai/codex)
|
||||
[](https://kiro.dev)
|
||||
[](https://kiro.dev)
|
||||
[](https://cursor.sh)
|
||||
[](https://github.com/features/copilot)
|
||||
[](https://github.com/opencode-ai/opencode)
|
||||
@@ -17,12 +17,13 @@
|
||||
|
||||
If this project helps you, you can [support it here](https://buymeacoffee.com/sickn33) or simply ⭐ the repo.
|
||||
|
||||
**Antigravity Awesome Skills** is a curated, battle-tested library of **891 high-performance agentic skills** designed to work seamlessly across all major AI coding assistants:
|
||||
**Antigravity Awesome Skills** is a curated, battle-tested library of **927 high-performance agentic skills** designed to work seamlessly across all major AI coding assistants:
|
||||
|
||||
- 🟣 **Claude Code** (Anthropic CLI)
|
||||
- 🔵 **Gemini CLI** (Google DeepMind)
|
||||
- 🟢 **Codex CLI** (OpenAI)
|
||||
https://github.com/sickn33/antigravity-awesome-skills/pull/107/conflict?name=skills_index.json&ancestor_oid=9aa6336a54e7308ff8b34c222969d18c89576c8d&base_oid=dab694b49578ec5f4a24879ce75d873b9b6cd113&head_oid=7c986794ed9f0666e004f8900cdce3c42ce393b1- 🟠 **Kiro CLI** (AWS)
|
||||
- 🟠 **Kiro CLI** (AWS)
|
||||
- 🟠 **Kiro IDE** (AWS)
|
||||
- 🔴 **Antigravity IDE** (Google DeepMind)
|
||||
- 🩵 **GitHub Copilot** (VSCode Extension)
|
||||
- 🟠 **Cursor** (AI-native IDE)
|
||||
@@ -41,7 +42,7 @@ This repository provides essential skills to transform your AI assistant into a
|
||||
- [🎁 Curated Collections (Bundles)](#curated-collections)
|
||||
- [🧭 Antigravity Workflows](#antigravity-workflows)
|
||||
- [📦 Features & Categories](#features--categories)
|
||||
- [📚 Browse 891+ Skills](#browse-891-skills)
|
||||
- [📚 Browse 927+ Skills](#browse-927-skills)
|
||||
- [🤝 How to Contribute](#how-to-contribute)
|
||||
- [🤝 Community](#community)
|
||||
- [☕ Support the Project](#support-the-project)
|
||||
@@ -55,11 +56,11 @@ This repository provides essential skills to transform your AI assistant into a
|
||||
|
||||
## New Here? Start Here!
|
||||
|
||||
**Welcome to the V6.0.0 Workflows Edition.** This isn't just a list of scripts; it's a complete operating system for your AI Agent.
|
||||
**Welcome to the V6.1.0 Workflows Edition.** This isn't just a list of scripts; it's a complete operating system for your AI Agent.
|
||||
|
||||
### 1. 🐣 Context: What is this?
|
||||
|
||||
**Antigravity Awesome Skills** (Release 6.0.0) is a massive upgrade to your AI's capabilities.
|
||||
**Antigravity Awesome Skills** (Release 6.1.0) is a massive upgrade to your AI's capabilities.
|
||||
|
||||
AI Agents (like Claude Code, Cursor, or Gemini) are smart, but they lack **specific tools**. They don't know your company's "Deployment Protocol" or the specific syntax for "AWS CloudFormation".
|
||||
**Skills** are small markdown files that teach them how to do these specific tasks perfectly, every time.
|
||||
@@ -107,12 +108,13 @@ Once installed, just ask your agent naturally:
|
||||
|
||||
These skills follow the universal **SKILL.md** format and work with any AI coding assistant that supports agentic skills.
|
||||
|
||||
| Tool | Type | Invocation Example | Path |
|
||||
| :-------------- | :--- | :-------------------------------- | :-------------------------------------------------------------------- |
|
||||
| **Claude Code** | CLI | `>> /skill-name help me...` | `.claude/skills/` |
|
||||
| **Gemini CLI** | CLI | `(User Prompt) Use skill-name...` | `.gemini/skills/` |
|
||||
| **Codex CLI** | CLI | `(User Prompt) Use skill-name...` | `.codex/skills/` |
|
||||
| **Kiro CLI** | CLI | `(User Prompt) Use skill-name...` | `.kiro/skills/` |
|
||||
| Tool | Type | Invocation Example | Path |
|
||||
| :-------------- | :--- | :-------------------------------- | :---------------- |
|
||||
| **Claude Code** | CLI | `>> /skill-name help me...` | `.claude/skills/` |
|
||||
| **Gemini CLI** | CLI | `(User Prompt) Use skill-name...` | `.gemini/skills/` |
|
||||
| **Codex CLI** | CLI | `(User Prompt) Use skill-name...` | `.codex/skills/` |
|
||||
| **Kiro CLI** | CLI | `(Auto) Skills load on-demand` | Global: `~/.kiro/skills/` · Workspace: `.kiro/skills/` |
|
||||
| **Kiro IDE** | IDE | `/skill-name or (Auto)` | Global: `~/.kiro/skills/` · Workspace: `.kiro/skills/` |
|
||||
| **Antigravity** | IDE | `(Agent Mode) Use skill...` | Global: `~/.gemini/antigravity/skills/` · Workspace: `.agent/skills/` |
|
||||
| **Cursor** | IDE | `@skill-name (in Chat)` | `.cursor/skills/` |
|
||||
| **Copilot** | Ext | `(Paste content manually)` | N/A |
|
||||
@@ -131,7 +133,7 @@ These skills follow the universal **SKILL.md** format and work with any AI codin
|
||||
|
||||
## Installation
|
||||
|
||||
To use these skills with **Claude Code**, **Gemini CLI**, **Codex CLI**, **Cursor**, **Antigravity**, **OpenCode**, or **AdaL**:
|
||||
To use these skills with **Claude Code**, **Gemini CLI**, **Codex CLI**, **Kiro CLI**, **Kiro IDE**, **Cursor**, **Antigravity**, **OpenCode**, or **AdaL**:
|
||||
|
||||
### Option A: npx (recommended)
|
||||
|
||||
@@ -142,6 +144,12 @@ npx antigravity-awesome-skills
|
||||
# Antigravity (explicit; same as default)
|
||||
npx antigravity-awesome-skills --antigravity
|
||||
|
||||
# Kiro CLI/IDE (global)
|
||||
npx antigravity-awesome-skills --path ~/.kiro/skills
|
||||
|
||||
# Kiro CLI/IDE (workspace)
|
||||
npx antigravity-awesome-skills --path .kiro/skills
|
||||
|
||||
# Cursor
|
||||
npx antigravity-awesome-skills --cursor
|
||||
|
||||
@@ -180,6 +188,12 @@ git clone https://github.com/sickn33/antigravity-awesome-skills.git ~/.gemini/an
|
||||
# Workspace-specific (e.g. .agent/skills in your project)
|
||||
git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skills
|
||||
|
||||
# Kiro CLI/IDE global
|
||||
git clone https://github.com/sickn33/antigravity-awesome-skills.git ~/.kiro/skills
|
||||
|
||||
# Kiro CLI/IDE workspace
|
||||
git clone https://github.com/sickn33/antigravity-awesome-skills.git .kiro/skills
|
||||
|
||||
# Claude Code specific
|
||||
git clone https://github.com/sickn33/antigravity-awesome-skills.git .claude/skills
|
||||
|
||||
@@ -199,6 +213,17 @@ git clone https://github.com/sickn33/antigravity-awesome-skills.git .cursor/skil
|
||||
git clone https://github.com/sickn33/antigravity-awesome-skills.git .agents/skills
|
||||
```
|
||||
|
||||
### Option C: Kiro IDE Import (GUI)
|
||||
|
||||
For Kiro IDE users, you can import individual skills directly:
|
||||
|
||||
1. Open **Agent Steering & Skills** panel in Kiro IDE
|
||||
2. Click **+** → **Import a skill** → **GitHub**
|
||||
3. Paste skill URL: `https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/[skill-name]`
|
||||
4. Example: `https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/aws-cost-optimizer`
|
||||
|
||||
> **Note**: This imports one skill at a time. For bulk installation, use Option A or B above.
|
||||
|
||||
---
|
||||
|
||||
## Troubleshooting
|
||||
@@ -246,7 +271,7 @@ npx antigravity-awesome-skills
|
||||
|
||||
**Bundles** are curated groups of skills for a specific role or goal (for example: `Web Wizard`, `Security Engineer`, `OSS Maintainer`).
|
||||
|
||||
They help you avoid picking from 889+ skills one by one.
|
||||
They help you avoid picking from 925+ skills one by one.
|
||||
|
||||
### ⚠️ Important: Bundles Are NOT Separate Installations!
|
||||
|
||||
@@ -318,7 +343,7 @@ The repository is organized into specialized domains to transform your AI into a
|
||||
|
||||
Counts change as new skills are added. For the current full registry, see [CATALOG.md](CATALOG.md).
|
||||
|
||||
## Browse 891+ Skills
|
||||
## Browse 927+ Skills
|
||||
|
||||
We have moved the full skill registry to a dedicated catalog to keep this README clean.
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 52 KiB After Width: | Height: | Size: 52 KiB |
@@ -4,6 +4,7 @@
|
||||
"accessibility-compliance-audit": "accessibility-compliance-accessibility-audit",
|
||||
"agent-orchestration-improve": "agent-orchestration-improve-agent",
|
||||
"agent-orchestration-optimize": "agent-orchestration-multi-agent-optimize",
|
||||
"android-jetpack-expert": "android-jetpack-compose-expert",
|
||||
"api-testing-mock": "api-testing-observability-api-mock",
|
||||
"templates": "app-builder/templates",
|
||||
"application-performance-optimization": "application-performance-performance-optimization",
|
||||
@@ -76,6 +77,11 @@
|
||||
"git-pr-workflow": "git-pr-workflows-git-workflow",
|
||||
"incident-response": "incident-response-incident-response",
|
||||
"javascript-typescript-scaffold": "javascript-typescript-typescript-scaffold",
|
||||
"base": "libreoffice/base",
|
||||
"calc": "libreoffice/calc",
|
||||
"draw": "libreoffice/draw",
|
||||
"impress": "libreoffice/impress",
|
||||
"writer": "libreoffice/writer",
|
||||
"llm-application-assistant": "llm-application-dev-ai-assistant",
|
||||
"llm-application-agent": "llm-application-dev-langchain-agent",
|
||||
"llm-application-optimize": "llm-application-dev-prompt-optimize",
|
||||
@@ -102,6 +108,7 @@
|
||||
"startup-business-projections": "startup-business-analyst-financial-projections",
|
||||
"startup-business-opportunity": "startup-business-analyst-market-opportunity",
|
||||
"systems-programming-project": "systems-programming-rust-project",
|
||||
"team-collaboration-notes": "team-collaboration-standup-notes"
|
||||
"team-collaboration-notes": "team-collaboration-standup-notes",
|
||||
"shopify—development": "shopify-development"
|
||||
}
|
||||
}
|
||||
@@ -7,12 +7,15 @@
|
||||
"3d-web-experience",
|
||||
"agent-framework-azure-ai-py",
|
||||
"algolia-search",
|
||||
"android-jetpack-compose-expert",
|
||||
"api-design-principles",
|
||||
"api-documentation",
|
||||
"api-documentation-generator",
|
||||
"api-documenter",
|
||||
"api-fuzzing-bug-bounty",
|
||||
"api-patterns",
|
||||
"api-security-best-practices",
|
||||
"api-security-testing",
|
||||
"api-testing-observability-api-mock",
|
||||
"app-store-optimization",
|
||||
"application-performance-performance-optimization",
|
||||
@@ -71,6 +74,7 @@
|
||||
"backend-dev-guidelines",
|
||||
"backend-development-feature-development",
|
||||
"backend-security-coder",
|
||||
"bevy-ecs-expert",
|
||||
"bullmq-specialist",
|
||||
"bun-development",
|
||||
"cc-skill-backend-patterns",
|
||||
@@ -83,8 +87,10 @@
|
||||
"dbos-golang",
|
||||
"dbos-python",
|
||||
"dbos-typescript",
|
||||
"development",
|
||||
"discord-bot-architect",
|
||||
"django-pro",
|
||||
"documentation",
|
||||
"documentation-generation-doc-generate",
|
||||
"documentation-templates",
|
||||
"dotnet-architect",
|
||||
@@ -145,6 +151,7 @@
|
||||
"product-manager-toolkit",
|
||||
"pydantic-models-py",
|
||||
"python-development-python-scaffold",
|
||||
"python-fastapi-development",
|
||||
"python-packaging",
|
||||
"python-patterns",
|
||||
"python-performance-optimization",
|
||||
@@ -155,6 +162,7 @@
|
||||
"react-flow-node-ts",
|
||||
"react-modernization",
|
||||
"react-native-architecture",
|
||||
"react-nextjs-development",
|
||||
"react-patterns",
|
||||
"react-state-management",
|
||||
"react-ui-patterns",
|
||||
@@ -163,6 +171,7 @@
|
||||
"ruby-pro",
|
||||
"rust-async-patterns",
|
||||
"rust-pro",
|
||||
"security-audit",
|
||||
"security/aws-secrets-rotation",
|
||||
"senior-architect",
|
||||
"senior-fullstack",
|
||||
@@ -188,6 +197,7 @@
|
||||
"voice-ai-development",
|
||||
"web-artifacts-builder",
|
||||
"webapp-testing",
|
||||
"wordpress-plugin-development",
|
||||
"zustand-store-ts"
|
||||
]
|
||||
},
|
||||
@@ -198,6 +208,7 @@
|
||||
"antigravity-workflows",
|
||||
"api-fuzzing-bug-bounty",
|
||||
"api-security-best-practices",
|
||||
"api-security-testing",
|
||||
"attack-tree-construction",
|
||||
"auth-implementation-patterns",
|
||||
"aws-penetration-testing",
|
||||
@@ -250,6 +261,7 @@
|
||||
"sast-configuration",
|
||||
"scanning-tools",
|
||||
"secrets-management",
|
||||
"security-audit",
|
||||
"security-auditor",
|
||||
"security-bluebook-builder",
|
||||
"security-compliance-compliance-check",
|
||||
@@ -270,7 +282,10 @@
|
||||
"top-web-vulnerabilities",
|
||||
"varlock-claude-skill",
|
||||
"vulnerability-scanner",
|
||||
"web-design-guidelines"
|
||||
"web-design-guidelines",
|
||||
"web-security-testing",
|
||||
"wordpress",
|
||||
"wordpress-plugin-development"
|
||||
]
|
||||
},
|
||||
"k8s-core": {
|
||||
@@ -280,6 +295,7 @@
|
||||
"azure-identity-java",
|
||||
"azure-identity-ts",
|
||||
"azure-servicebus-ts",
|
||||
"cloud-devops",
|
||||
"freshservice-automation",
|
||||
"gitops-workflow",
|
||||
"helm-chart-scaffolding",
|
||||
@@ -287,8 +303,10 @@
|
||||
"k8s-manifest-generator",
|
||||
"k8s-security-policies",
|
||||
"kubernetes-architect",
|
||||
"kubernetes-deployment",
|
||||
"legal-advisor",
|
||||
"linkerd-patterns",
|
||||
"linux-troubleshooting",
|
||||
"microservices-patterns",
|
||||
"moodle-external-api-development",
|
||||
"mtls-configuration",
|
||||
@@ -325,6 +343,8 @@
|
||||
"data-quality-frameworks",
|
||||
"data-scientist",
|
||||
"data-storytelling",
|
||||
"data-structure-protocol",
|
||||
"database",
|
||||
"database-admin",
|
||||
"database-architect",
|
||||
"database-cloud-optimization-cost-optimize",
|
||||
@@ -343,6 +363,8 @@
|
||||
"googlesheets-automation",
|
||||
"graphql",
|
||||
"kpi-dashboard-design",
|
||||
"libreoffice/base",
|
||||
"libreoffice/calc",
|
||||
"loki-mode",
|
||||
"mailchimp-automation",
|
||||
"ml-pipeline-workflow",
|
||||
@@ -354,8 +376,10 @@
|
||||
"php-pro",
|
||||
"postgres-best-practices",
|
||||
"postgresql",
|
||||
"postgresql-optimization",
|
||||
"prisma-expert",
|
||||
"pydantic-models-py",
|
||||
"rag-implementation",
|
||||
"react-ui-patterns",
|
||||
"segment-cdp",
|
||||
"sendgrid-automation",
|
||||
@@ -387,6 +411,7 @@
|
||||
"azure-monitor-opentelemetry-ts",
|
||||
"backend-development-feature-development",
|
||||
"cicd-automation-workflow-automate",
|
||||
"cloud-devops",
|
||||
"code-review-ai-ai-review",
|
||||
"data-engineering-data-pipeline",
|
||||
"database-migrations-migration-observability",
|
||||
@@ -414,6 +439,7 @@
|
||||
"incident-response-smart-fix",
|
||||
"incident-runbook-templates",
|
||||
"kpi-dashboard-design",
|
||||
"kubernetes-deployment",
|
||||
"langfuse",
|
||||
"llm-app-patterns",
|
||||
"loki-mode",
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "antigravity-awesome-skills",
|
||||
"version": "6.0.0",
|
||||
"description": "883+ agentic skills for Claude Code, Gemini CLI, Cursor, Antigravity & more. Installer CLI.",
|
||||
"version": "6.1.0",
|
||||
"description": "925+ agentic skills for Claude Code, Gemini CLI, Cursor, Antigravity & more. Installer CLI.",
|
||||
"license": "MIT",
|
||||
"scripts": {
|
||||
"validate": "python3 scripts/validate_skills.py",
|
||||
|
||||
30
release_notes.md
Normal file
30
release_notes.md
Normal file
@@ -0,0 +1,30 @@
|
||||
## v6.1.0 - Issues Fix & Community Expansion
|
||||
|
||||
**Bugfixes for #116 and #120, plus Game Dev bundle, Android skills, Workflow Bundles, LibreOffice, Data Structure Protocol, and Kiro IDE support.**
|
||||
|
||||
This release fixes the YAML syntax error in database-migrations-sql-migrations (issue #116), adds a typo alias so `shopify—development` (em dash) resolves to `shopify-development` (issue #120), and ships a large set of community PRs: Game Development Expansion (Bevy ECS, GLSL, Godot 4), Android Modern Development (Compose + Coroutines), Workflow Bundles and LibreOffice skills, Data Structure Protocol, and Kiro CLI/IDE support.
|
||||
|
||||
### New Skills
|
||||
|
||||
- **Game Development Expansion** (PR #121): `bevy-ecs-expert`, `shader-programming-glsl`, `godot-4-migration`.
|
||||
- **Android Modern Development** (PR #118): `android-jetpack-compose-expert`, `kotlin-coroutines-expert`.
|
||||
- **Workflow Bundles & LibreOffice** (PR #113): Workflow bundles readme, LibreOffice skills (Base, Calc, Draw, Impress, Writer), plus office-productivity, WordPress suite, and many domain skills.
|
||||
- **Data Structure Protocol** (PR #114): `data-structure-protocol`.
|
||||
- **Kiro CLI and Kiro IDE** (PR #122): Documentation and support for Kiro.
|
||||
|
||||
### Improvements
|
||||
|
||||
- **YAML fix** (PR #119, fixes #116): Resolved invalid YAML in `database-migrations-sql-migrations/SKILL.md`.
|
||||
- **Skill matching** (fixes #120): Added typo alias `shopify—development` → `shopify-development`.
|
||||
- **Registry**: Now tracking 925 skills.
|
||||
|
||||
### Credits
|
||||
|
||||
- **@nikolasdehor** for YAML fix (PR #119), Game Development Expansion (PR #121), Android Modern Development (PR #118)
|
||||
- **@ssumanbiswas** for Kiro CLI and Kiro IDE support (PR #122)
|
||||
- **@munir-abbasi** for Workflow Bundles and LibreOffice Skills (PR #113)
|
||||
- **@k-kolomeitsev** for Data Structure Protocol (PR #114)
|
||||
|
||||
---
|
||||
|
||||
_Upgrade: `git pull origin main` or `npx antigravity-awesome-skills`_
|
||||
@@ -480,6 +480,11 @@ function buildTriggers(skill, tags) {
|
||||
return unique([...tags, ...tokens]).slice(0, 12);
|
||||
}
|
||||
|
||||
/** Common typo aliases (e.g. em dash — instead of hyphen -) for skill lookup. */
|
||||
const TYPO_ALIASES = {
|
||||
"shopify—development": "shopify-development",
|
||||
};
|
||||
|
||||
function buildAliases(skills) {
|
||||
const existingIds = new Set(skills.map((skill) => skill.id));
|
||||
const aliases = {};
|
||||
@@ -518,6 +523,12 @@ function buildAliases(skills) {
|
||||
used.add(alias);
|
||||
}
|
||||
|
||||
for (const [typo, canonicalId] of Object.entries(TYPO_ALIASES)) {
|
||||
if (existingIds.has(canonicalId) && !aliases[typo]) {
|
||||
aliases[typo] = canonicalId;
|
||||
}
|
||||
}
|
||||
|
||||
return aliases;
|
||||
}
|
||||
|
||||
|
||||
174
skills/ai-agent-development/SKILL.md
Normal file
174
skills/ai-agent-development/SKILL.md
Normal file
@@ -0,0 +1,174 @@
|
||||
---
|
||||
name: ai-agent-development
|
||||
description: "AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: ai-ml
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# AI Agent Development Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for building AI agents including single autonomous agents, multi-agent systems, agent orchestration, tool integration, and human-in-the-loop patterns.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Building autonomous AI agents
|
||||
- Creating multi-agent systems
|
||||
- Implementing agent orchestration
|
||||
- Adding tool integration to agents
|
||||
- Setting up agent memory
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Agent Design
|
||||
|
||||
#### Skills to Invoke
|
||||
- `ai-agents-architect` - Agent architecture
|
||||
- `autonomous-agents` - Autonomous patterns
|
||||
|
||||
#### Actions
|
||||
1. Define agent purpose
|
||||
2. Design agent capabilities
|
||||
3. Plan tool integration
|
||||
4. Design memory system
|
||||
5. Define success metrics
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @ai-agents-architect to design AI agent architecture
|
||||
```
|
||||
|
||||
### Phase 2: Single Agent Implementation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `autonomous-agent-patterns` - Agent patterns
|
||||
- `autonomous-agents` - Autonomous agents
|
||||
|
||||
#### Actions
|
||||
1. Choose agent framework
|
||||
2. Implement agent logic
|
||||
3. Add tool integration
|
||||
4. Configure memory
|
||||
5. Test agent behavior
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @autonomous-agent-patterns to implement single agent
|
||||
```
|
||||
|
||||
### Phase 3: Multi-Agent System
|
||||
|
||||
#### Skills to Invoke
|
||||
- `crewai` - CrewAI framework
|
||||
- `multi-agent-patterns` - Multi-agent patterns
|
||||
|
||||
#### Actions
|
||||
1. Define agent roles
|
||||
2. Set up agent communication
|
||||
3. Configure orchestration
|
||||
4. Implement task delegation
|
||||
5. Test coordination
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @crewai to build multi-agent system with roles
|
||||
```
|
||||
|
||||
### Phase 4: Agent Orchestration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `langgraph` - LangGraph orchestration
|
||||
- `workflow-orchestration-patterns` - Orchestration
|
||||
|
||||
#### Actions
|
||||
1. Design workflow graph
|
||||
2. Implement state management
|
||||
3. Add conditional branches
|
||||
4. Configure persistence
|
||||
5. Test workflows
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @langgraph to create stateful agent workflows
|
||||
```
|
||||
|
||||
### Phase 5: Tool Integration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `agent-tool-builder` - Tool building
|
||||
- `tool-design` - Tool design
|
||||
|
||||
#### Actions
|
||||
1. Identify tool needs
|
||||
2. Design tool interfaces
|
||||
3. Implement tools
|
||||
4. Add error handling
|
||||
5. Test tool usage
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @agent-tool-builder to create agent tools
|
||||
```
|
||||
|
||||
### Phase 6: Memory Systems
|
||||
|
||||
#### Skills to Invoke
|
||||
- `agent-memory-systems` - Memory architecture
|
||||
- `conversation-memory` - Conversation memory
|
||||
|
||||
#### Actions
|
||||
1. Design memory structure
|
||||
2. Implement short-term memory
|
||||
3. Set up long-term memory
|
||||
4. Add entity memory
|
||||
5. Test memory retrieval
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @agent-memory-systems to implement agent memory
|
||||
```
|
||||
|
||||
### Phase 7: Evaluation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `agent-evaluation` - Agent evaluation
|
||||
- `evaluation` - AI evaluation
|
||||
|
||||
#### Actions
|
||||
1. Define evaluation criteria
|
||||
2. Create test scenarios
|
||||
3. Measure agent performance
|
||||
4. Test edge cases
|
||||
5. Iterate improvements
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @agent-evaluation to evaluate agent performance
|
||||
```
|
||||
|
||||
## Agent Architecture
|
||||
|
||||
```
|
||||
User Input -> Planner -> Agent -> Tools -> Memory -> Response
|
||||
| | | |
|
||||
Decompose LLM Core Actions Short/Long-term
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Agent logic working
|
||||
- [ ] Tools integrated
|
||||
- [ ] Memory functional
|
||||
- [ ] Orchestration tested
|
||||
- [ ] Evaluation passing
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `ai-ml` - AI/ML development
|
||||
- `rag-implementation` - RAG systems
|
||||
- `workflow-automation` - Workflow patterns
|
||||
253
skills/ai-ml/SKILL.md
Normal file
253
skills/ai-ml/SKILL.md
Normal file
@@ -0,0 +1,253 @@
|
||||
---
|
||||
name: ai-ml
|
||||
description: "AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: artificial-intelligence
|
||||
category: workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# AI/ML Workflow Bundle
|
||||
|
||||
## Overview
|
||||
|
||||
Comprehensive AI/ML workflow for building LLM applications, implementing RAG systems, creating AI agents, and developing machine learning pipelines. This bundle orchestrates skills for production AI development.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Building LLM-powered applications
|
||||
- Implementing RAG (Retrieval-Augmented Generation)
|
||||
- Creating AI agents
|
||||
- Developing ML pipelines
|
||||
- Adding AI features to applications
|
||||
- Setting up AI observability
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: AI Application Design
|
||||
|
||||
#### Skills to Invoke
|
||||
- `ai-product` - AI product development
|
||||
- `ai-engineer` - AI engineering
|
||||
- `ai-agents-architect` - Agent architecture
|
||||
- `llm-app-patterns` - LLM patterns
|
||||
|
||||
#### Actions
|
||||
1. Define AI use cases
|
||||
2. Choose appropriate models
|
||||
3. Design system architecture
|
||||
4. Plan data flows
|
||||
5. Define success metrics
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @ai-product to design AI-powered features
|
||||
```
|
||||
|
||||
```
|
||||
Use @ai-agents-architect to design multi-agent system
|
||||
```
|
||||
|
||||
### Phase 2: LLM Integration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `llm-application-dev-ai-assistant` - AI assistant development
|
||||
- `llm-application-dev-langchain-agent` - LangChain agents
|
||||
- `llm-application-dev-prompt-optimize` - Prompt engineering
|
||||
- `gemini-api-dev` - Gemini API
|
||||
|
||||
#### Actions
|
||||
1. Select LLM provider
|
||||
2. Set up API access
|
||||
3. Implement prompt templates
|
||||
4. Configure model parameters
|
||||
5. Add streaming support
|
||||
6. Implement error handling
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @llm-application-dev-ai-assistant to build conversational AI
|
||||
```
|
||||
|
||||
```
|
||||
Use @llm-application-dev-langchain-agent to create LangChain agents
|
||||
```
|
||||
|
||||
```
|
||||
Use @llm-application-dev-prompt-optimize to optimize prompts
|
||||
```
|
||||
|
||||
### Phase 3: RAG Implementation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `rag-engineer` - RAG engineering
|
||||
- `rag-implementation` - RAG implementation
|
||||
- `embedding-strategies` - Embedding selection
|
||||
- `vector-database-engineer` - Vector databases
|
||||
- `similarity-search-patterns` - Similarity search
|
||||
- `hybrid-search-implementation` - Hybrid search
|
||||
|
||||
#### Actions
|
||||
1. Design data pipeline
|
||||
2. Choose embedding model
|
||||
3. Set up vector database
|
||||
4. Implement chunking strategy
|
||||
5. Configure retrieval
|
||||
6. Add reranking
|
||||
7. Implement caching
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @rag-engineer to design RAG pipeline
|
||||
```
|
||||
|
||||
```
|
||||
Use @vector-database-engineer to set up vector search
|
||||
```
|
||||
|
||||
```
|
||||
Use @embedding-strategies to select optimal embeddings
|
||||
```
|
||||
|
||||
### Phase 4: AI Agent Development
|
||||
|
||||
#### Skills to Invoke
|
||||
- `autonomous-agents` - Autonomous agent patterns
|
||||
- `autonomous-agent-patterns` - Agent patterns
|
||||
- `crewai` - CrewAI framework
|
||||
- `langgraph` - LangGraph
|
||||
- `multi-agent-patterns` - Multi-agent systems
|
||||
- `computer-use-agents` - Computer use agents
|
||||
|
||||
#### Actions
|
||||
1. Design agent architecture
|
||||
2. Define agent roles
|
||||
3. Implement tool integration
|
||||
4. Set up memory systems
|
||||
5. Configure orchestration
|
||||
6. Add human-in-the-loop
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @crewai to build role-based multi-agent system
|
||||
```
|
||||
|
||||
```
|
||||
Use @langgraph to create stateful AI workflows
|
||||
```
|
||||
|
||||
```
|
||||
Use @autonomous-agents to design autonomous agent
|
||||
```
|
||||
|
||||
### Phase 5: ML Pipeline Development
|
||||
|
||||
#### Skills to Invoke
|
||||
- `ml-engineer` - ML engineering
|
||||
- `mlops-engineer` - MLOps
|
||||
- `machine-learning-ops-ml-pipeline` - ML pipelines
|
||||
- `ml-pipeline-workflow` - ML workflows
|
||||
- `data-engineer` - Data engineering
|
||||
|
||||
#### Actions
|
||||
1. Design ML pipeline
|
||||
2. Set up data processing
|
||||
3. Implement model training
|
||||
4. Configure evaluation
|
||||
5. Set up model registry
|
||||
6. Deploy models
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @ml-engineer to build machine learning pipeline
|
||||
```
|
||||
|
||||
```
|
||||
Use @mlops-engineer to set up MLOps infrastructure
|
||||
```
|
||||
|
||||
### Phase 6: AI Observability
|
||||
|
||||
#### Skills to Invoke
|
||||
- `langfuse` - Langfuse observability
|
||||
- `manifest` - Manifest telemetry
|
||||
- `evaluation` - AI evaluation
|
||||
- `llm-evaluation` - LLM evaluation
|
||||
|
||||
#### Actions
|
||||
1. Set up tracing
|
||||
2. Configure logging
|
||||
3. Implement evaluation
|
||||
4. Monitor performance
|
||||
5. Track costs
|
||||
6. Set up alerts
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @langfuse to set up LLM observability
|
||||
```
|
||||
|
||||
```
|
||||
Use @evaluation to create evaluation framework
|
||||
```
|
||||
|
||||
### Phase 7: AI Security
|
||||
|
||||
#### Skills to Invoke
|
||||
- `prompt-engineering` - Prompt security
|
||||
- `security-scanning-security-sast` - Security scanning
|
||||
|
||||
#### Actions
|
||||
1. Implement input validation
|
||||
2. Add output filtering
|
||||
3. Configure rate limiting
|
||||
4. Set up access controls
|
||||
5. Monitor for abuse
|
||||
6. Implement audit logging
|
||||
|
||||
## AI Development Checklist
|
||||
|
||||
### LLM Integration
|
||||
- [ ] API keys secured
|
||||
- [ ] Rate limiting configured
|
||||
- [ ] Error handling implemented
|
||||
- [ ] Streaming enabled
|
||||
- [ ] Token usage tracked
|
||||
|
||||
### RAG System
|
||||
- [ ] Data pipeline working
|
||||
- [ ] Embeddings generated
|
||||
- [ ] Vector search optimized
|
||||
- [ ] Retrieval accuracy tested
|
||||
- [ ] Caching implemented
|
||||
|
||||
### AI Agents
|
||||
- [ ] Agent roles defined
|
||||
- [ ] Tools integrated
|
||||
- [ ] Memory working
|
||||
- [ ] Orchestration tested
|
||||
- [ ] Error handling robust
|
||||
|
||||
### Observability
|
||||
- [ ] Tracing enabled
|
||||
- [ ] Metrics collected
|
||||
- [ ] Evaluation running
|
||||
- [ ] Alerts configured
|
||||
- [ ] Dashboards created
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] All AI features tested
|
||||
- [ ] Performance benchmarks met
|
||||
- [ ] Security measures in place
|
||||
- [ ] Observability configured
|
||||
- [ ] Documentation complete
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - Application development
|
||||
- `database` - Data management
|
||||
- `cloud-devops` - Infrastructure
|
||||
- `testing-qa` - AI testing
|
||||
152
skills/android-jetpack-compose-expert/SKILL.md
Normal file
152
skills/android-jetpack-compose-expert/SKILL.md
Normal file
@@ -0,0 +1,152 @@
|
||||
---
|
||||
name: android-jetpack-compose-expert
|
||||
description: Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.
|
||||
risk: safe
|
||||
source: community
|
||||
---
|
||||
|
||||
# Android Jetpack Compose Expert
|
||||
|
||||
## Overview
|
||||
|
||||
A comprehensive guide for building production-quality Android applications using Jetpack Compose. This skill covers architectural patterns, state management with ViewModels, navigation type-safety, and performance optimization techniques.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
- Use when starting a new Android project with Jetpack Compose.
|
||||
- Use when migrating legacy XML layouts to Compose.
|
||||
- Use when implementing complex UI state management and side effects.
|
||||
- Use when optimizing Compose performance (recomposition counts, stability).
|
||||
- Use when setting up Navigation with type safety.
|
||||
|
||||
## Step-by-Step Guide
|
||||
|
||||
### 1. Project Setup & Dependencies
|
||||
|
||||
Ensure your `libs.versions.toml` includes the necessary Compose BOM and libraries.
|
||||
|
||||
```kotlin
|
||||
[versions]
|
||||
composeBom = "2024.02.01"
|
||||
activityCompose = "1.8.2"
|
||||
|
||||
[libraries]
|
||||
androidx-compose-bom = { group = "androidx.compose", name = "compose-bom", version.ref = "composeBom" }
|
||||
androidx-ui = { group = "androidx.compose.ui", name = "ui" }
|
||||
androidx-ui-graphics = { group = "androidx.compose.ui", name = "ui-graphics" }
|
||||
androidx-ui-tooling-preview = { group = "androidx.compose.ui", name = "ui-tooling-preview" }
|
||||
androidx-material3 = { group = "androidx.compose.material3", name = "material3" }
|
||||
androidx-activity-compose = { group = "androidx.activity", name = "activity-compose", version.ref = "activityCompose" }
|
||||
```
|
||||
|
||||
### 2. State Management Pattern (MVI/MVVM)
|
||||
|
||||
Use `ViewModel` with `StateFlow` to expose UI state. Avoid exposing `MutableStateFlow`.
|
||||
|
||||
```kotlin
|
||||
// UI State Definition
|
||||
data class UserUiState(
|
||||
val isLoading: Boolean = false,
|
||||
val user: User? = null,
|
||||
val error: String? = null
|
||||
)
|
||||
|
||||
// ViewModel
|
||||
class UserViewModel @Inject constructor(
|
||||
private val userRepository: UserRepository
|
||||
) : ViewModel() {
|
||||
|
||||
private val _uiState = MutableStateFlow(UserUiState())
|
||||
val uiState: StateFlow<UserUiState> = _uiState.asStateFlow()
|
||||
|
||||
fun loadUser() {
|
||||
viewModelScope.launch {
|
||||
_uiState.update { it.copy(isLoading = true) }
|
||||
try {
|
||||
val user = userRepository.getUser()
|
||||
_uiState.update { it.copy(user = user, isLoading = false) }
|
||||
} catch (e: Exception) {
|
||||
_uiState.update { it.copy(error = e.message, isLoading = false) }
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### 3. Creating the Screen Composable
|
||||
|
||||
Consume the state in a "Screen" composable and pass data down to stateless components.
|
||||
|
||||
```kotlin
|
||||
@Composable
|
||||
fun UserScreen(
|
||||
viewModel: UserViewModel = hiltViewModel()
|
||||
) {
|
||||
val uiState by viewModel.uiState.collectAsStateWithLifecycle()
|
||||
|
||||
UserContent(
|
||||
uiState = uiState,
|
||||
onRetry = viewModel::loadUser
|
||||
)
|
||||
}
|
||||
|
||||
@Composable
|
||||
fun UserContent(
|
||||
uiState: UserUiState,
|
||||
onRetry: () -> Unit
|
||||
) {
|
||||
Scaffold { padding ->
|
||||
Box(modifier = Modifier.padding(padding)) {
|
||||
when {
|
||||
uiState.isLoading -> CircularProgressIndicator()
|
||||
uiState.error != null -> ErrorView(uiState.error, onRetry)
|
||||
uiState.user != null -> UserProfile(uiState.user)
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Type-Safe Navigation
|
||||
|
||||
Using the new Navigation Compose Type Safety (available in recent versions).
|
||||
|
||||
```kotlin
|
||||
// Define Destinations
|
||||
@Serializable
|
||||
object Home
|
||||
|
||||
@Serializable
|
||||
data class Profile(val userId: String)
|
||||
|
||||
// Setup NavHost
|
||||
@Composable
|
||||
fun AppNavHost(navController: NavHostController) {
|
||||
NavHost(navController, startDestination = Home) {
|
||||
composable<Home> {
|
||||
HomeScreen(onNavigateToProfile = { id ->
|
||||
navController.navigate(Profile(userId = id))
|
||||
})
|
||||
}
|
||||
composable<Profile> { backStackEntry ->
|
||||
val profile: Profile = backStackEntry.toRoute()
|
||||
ProfileScreen(userId = profile.userId)
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
- ✅ **Do:** Use `remember` and `derivedStateOf` to minimize unnecessary calculations during recomposition.
|
||||
- ✅ **Do:** Mark data classes used in UI state as `@Immutable` or `@Stable` if they contain `List` or other unstable types to enable smart recomposition skipping.
|
||||
- ✅ **Do:** Use `LaunchedEffect` for one-off side effects (like showing a Snackbar) triggered by state changes.
|
||||
- ❌ **Don't:** Perform expensive operations (like sorting a list) directly inside the Composable function body without `remember`.
|
||||
- ❌ **Don't:** Pass `ViewModel` instances down to child components. Pass only the data (state) and lambda callbacks (events).
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
**Problem:** Infinite Recomposition loop.
|
||||
**Solution:** Check if you are creating new object instances (like `List` or `Modifier`) inside the composition without `remember`, or if you are updating state inside the composition phase instead of a side-effect or callback. Use Layout Inspector to debug recomposition counts.
|
||||
164
skills/api-documentation/SKILL.md
Normal file
164
skills/api-documentation/SKILL.md
Normal file
@@ -0,0 +1,164 @@
|
||||
---
|
||||
name: api-documentation
|
||||
description: "API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: documentation
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# API Documentation Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for creating comprehensive API documentation including OpenAPI/Swagger specs, developer guides, code examples, and interactive documentation.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Creating API documentation
|
||||
- Generating OpenAPI specs
|
||||
- Writing developer guides
|
||||
- Adding code examples
|
||||
- Setting up API portals
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: API Discovery
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-documenter` - API documentation
|
||||
- `api-design-principles` - API design
|
||||
|
||||
#### Actions
|
||||
1. Inventory endpoints
|
||||
2. Document request/response
|
||||
3. Identify authentication
|
||||
4. Map error codes
|
||||
5. Note rate limits
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-documenter to discover and document API endpoints
|
||||
```
|
||||
|
||||
### Phase 2: OpenAPI Specification
|
||||
|
||||
#### Skills to Invoke
|
||||
- `openapi-spec-generation` - OpenAPI
|
||||
- `api-documenter` - API specs
|
||||
|
||||
#### Actions
|
||||
1. Create OpenAPI schema
|
||||
2. Define paths
|
||||
3. Add schemas
|
||||
4. Configure security
|
||||
5. Add examples
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @openapi-spec-generation to create OpenAPI specification
|
||||
```
|
||||
|
||||
### Phase 3: Developer Guide
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-documentation-generator` - Documentation
|
||||
- `documentation-templates` - Templates
|
||||
|
||||
#### Actions
|
||||
1. Create getting started
|
||||
2. Write authentication guide
|
||||
3. Document common patterns
|
||||
4. Add troubleshooting
|
||||
5. Create FAQ
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-documentation-generator to create developer guide
|
||||
```
|
||||
|
||||
### Phase 4: Code Examples
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-documenter` - Code examples
|
||||
- `tutorial-engineer` - Tutorials
|
||||
|
||||
#### Actions
|
||||
1. Create example requests
|
||||
2. Write SDK examples
|
||||
3. Add curl examples
|
||||
4. Create tutorials
|
||||
5. Test examples
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-documenter to generate code examples
|
||||
```
|
||||
|
||||
### Phase 5: Interactive Docs
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-documenter` - Interactive docs
|
||||
|
||||
#### Actions
|
||||
1. Set up Swagger UI
|
||||
2. Configure Redoc
|
||||
3. Add try-it functionality
|
||||
4. Test interactivity
|
||||
5. Deploy docs
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-documenter to set up interactive documentation
|
||||
```
|
||||
|
||||
### Phase 6: Documentation Site
|
||||
|
||||
#### Skills to Invoke
|
||||
- `docs-architect` - Documentation architecture
|
||||
- `wiki-page-writer` - Documentation
|
||||
|
||||
#### Actions
|
||||
1. Choose platform
|
||||
2. Design structure
|
||||
3. Create pages
|
||||
4. Add navigation
|
||||
5. Configure search
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @docs-architect to design API documentation site
|
||||
```
|
||||
|
||||
### Phase 7: Maintenance
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-documenter` - Doc maintenance
|
||||
|
||||
#### Actions
|
||||
1. Set up auto-generation
|
||||
2. Configure validation
|
||||
3. Add review process
|
||||
4. Schedule updates
|
||||
5. Monitor feedback
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-documenter to set up automated doc generation
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] OpenAPI spec complete
|
||||
- [ ] Developer guide written
|
||||
- [ ] Code examples working
|
||||
- [ ] Interactive docs functional
|
||||
- [ ] Documentation deployed
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `documentation` - Documentation
|
||||
- `api-development` - API development
|
||||
- `development` - Development
|
||||
172
skills/api-security-testing/SKILL.md
Normal file
172
skills/api-security-testing/SKILL.md
Normal file
@@ -0,0 +1,172 @@
|
||||
---
|
||||
name: api-security-testing
|
||||
description: "API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: security
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# API Security Testing Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for testing REST and GraphQL API security including authentication, authorization, rate limiting, input validation, and API-specific vulnerabilities.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Testing REST API security
|
||||
- Assessing GraphQL endpoints
|
||||
- Validating API authentication
|
||||
- Testing API rate limiting
|
||||
- Bug bounty API testing
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: API Discovery
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-fuzzing-bug-bounty` - API fuzzing
|
||||
- `scanning-tools` - API scanning
|
||||
|
||||
#### Actions
|
||||
1. Enumerate endpoints
|
||||
2. Document API methods
|
||||
3. Identify parameters
|
||||
4. Map data flows
|
||||
5. Review documentation
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-fuzzing-bug-bounty to discover API endpoints
|
||||
```
|
||||
|
||||
### Phase 2: Authentication Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `broken-authentication` - Auth testing
|
||||
- `api-security-best-practices` - API auth
|
||||
|
||||
#### Actions
|
||||
1. Test API key validation
|
||||
2. Test JWT tokens
|
||||
3. Test OAuth2 flows
|
||||
4. Test token expiration
|
||||
5. Test refresh tokens
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @broken-authentication to test API authentication
|
||||
```
|
||||
|
||||
### Phase 3: Authorization Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `idor-testing` - IDOR testing
|
||||
|
||||
#### Actions
|
||||
1. Test object-level authorization
|
||||
2. Test function-level authorization
|
||||
3. Test role-based access
|
||||
4. Test privilege escalation
|
||||
5. Test multi-tenant isolation
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @idor-testing to test API authorization
|
||||
```
|
||||
|
||||
### Phase 4: Input Validation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-fuzzing-bug-bounty` - API fuzzing
|
||||
- `sql-injection-testing` - Injection testing
|
||||
|
||||
#### Actions
|
||||
1. Test parameter validation
|
||||
2. Test SQL injection
|
||||
3. Test NoSQL injection
|
||||
4. Test command injection
|
||||
5. Test XXE injection
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-fuzzing-bug-bounty to fuzz API parameters
|
||||
```
|
||||
|
||||
### Phase 5: Rate Limiting
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-security-best-practices` - Rate limiting
|
||||
|
||||
#### Actions
|
||||
1. Test rate limit headers
|
||||
2. Test brute force protection
|
||||
3. Test resource exhaustion
|
||||
4. Test bypass techniques
|
||||
5. Document limitations
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-security-best-practices to test rate limiting
|
||||
```
|
||||
|
||||
### Phase 6: GraphQL Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-fuzzing-bug-bounty` - GraphQL fuzzing
|
||||
|
||||
#### Actions
|
||||
1. Test introspection
|
||||
2. Test query depth
|
||||
3. Test query complexity
|
||||
4. Test batch queries
|
||||
5. Test field suggestions
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-fuzzing-bug-bounty to test GraphQL security
|
||||
```
|
||||
|
||||
### Phase 7: Error Handling
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-security-best-practices` - Error handling
|
||||
|
||||
#### Actions
|
||||
1. Test error messages
|
||||
2. Check information disclosure
|
||||
3. Test stack traces
|
||||
4. Verify logging
|
||||
5. Document findings
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-security-best-practices to audit API error handling
|
||||
```
|
||||
|
||||
## API Security Checklist
|
||||
|
||||
- [ ] Authentication working
|
||||
- [ ] Authorization enforced
|
||||
- [ ] Input validated
|
||||
- [ ] Rate limiting active
|
||||
- [ ] Errors sanitized
|
||||
- [ ] Logging enabled
|
||||
- [ ] CORS configured
|
||||
- [ ] HTTPS enforced
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] All endpoints tested
|
||||
- [ ] Vulnerabilities documented
|
||||
- [ ] Remediation provided
|
||||
- [ ] Report generated
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `security-audit` - Security auditing
|
||||
- `web-security-testing` - Web security
|
||||
- `api-development` - API development
|
||||
197
skills/bash-scripting/SKILL.md
Normal file
197
skills/bash-scripting/SKILL.md
Normal file
@@ -0,0 +1,197 @@
|
||||
---
|
||||
name: bash-scripting
|
||||
description: "Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: system-administration
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Bash Scripting Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for creating robust, production-ready bash scripts with defensive programming patterns, comprehensive error handling, and automated testing.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Creating automation scripts
|
||||
- Writing system administration tools
|
||||
- Building deployment scripts
|
||||
- Developing backup solutions
|
||||
- Creating CI/CD scripts
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Script Design
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-pro` - Professional scripting
|
||||
- `bash-defensive-patterns` - Defensive patterns
|
||||
|
||||
#### Actions
|
||||
1. Define script purpose
|
||||
2. Identify inputs/outputs
|
||||
3. Plan error handling
|
||||
4. Design logging strategy
|
||||
5. Document requirements
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @bash-pro to design production-ready bash script
|
||||
```
|
||||
|
||||
### Phase 2: Script Structure
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-pro` - Script structure
|
||||
- `bash-defensive-patterns` - Safety patterns
|
||||
|
||||
#### Actions
|
||||
1. Add shebang and strict mode
|
||||
2. Create usage function
|
||||
3. Implement argument parsing
|
||||
4. Set up logging
|
||||
5. Add cleanup handlers
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @bash-defensive-patterns to implement strict mode and error handling
|
||||
```
|
||||
|
||||
### Phase 3: Core Implementation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-linux` - Linux commands
|
||||
- `linux-shell-scripting` - Shell scripting
|
||||
|
||||
#### Actions
|
||||
1. Implement main functions
|
||||
2. Add input validation
|
||||
3. Create helper functions
|
||||
4. Handle edge cases
|
||||
5. Add progress indicators
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @bash-linux to implement system commands
|
||||
```
|
||||
|
||||
### Phase 4: Error Handling
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-defensive-patterns` - Error handling
|
||||
- `error-handling-patterns` - Error patterns
|
||||
|
||||
#### Actions
|
||||
1. Add trap handlers
|
||||
2. Implement retry logic
|
||||
3. Create error messages
|
||||
4. Set up exit codes
|
||||
5. Add rollback capability
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @bash-defensive-patterns to add comprehensive error handling
|
||||
```
|
||||
|
||||
### Phase 5: Logging
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-pro` - Logging patterns
|
||||
|
||||
#### Actions
|
||||
1. Create logging function
|
||||
2. Add log levels
|
||||
3. Implement timestamps
|
||||
4. Configure log rotation
|
||||
5. Add debug mode
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @bash-pro to implement structured logging
|
||||
```
|
||||
|
||||
### Phase 6: Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bats-testing-patterns` - Bats testing
|
||||
- `shellcheck-configuration` - ShellCheck
|
||||
|
||||
#### Actions
|
||||
1. Write Bats tests
|
||||
2. Run ShellCheck
|
||||
3. Test edge cases
|
||||
4. Verify error handling
|
||||
5. Test with different inputs
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @bats-testing-patterns to write script tests
|
||||
```
|
||||
|
||||
```
|
||||
Use @shellcheck-configuration to lint bash script
|
||||
```
|
||||
|
||||
### Phase 7: Documentation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `documentation-templates` - Documentation
|
||||
|
||||
#### Actions
|
||||
1. Add script header
|
||||
2. Document functions
|
||||
3. Create usage examples
|
||||
4. List dependencies
|
||||
5. Add troubleshooting section
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @documentation-templates to document bash script
|
||||
```
|
||||
|
||||
## Script Template
|
||||
|
||||
```bash
|
||||
#!/usr/bin/env bash
|
||||
set -euo pipefail
|
||||
|
||||
readonly SCRIPT_NAME=$(basename "$0")
|
||||
readonly SCRIPT_DIR=$(cd "$(dirname "$0")" && pwd)
|
||||
|
||||
log() { echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*"; }
|
||||
error() { log "ERROR: $*" >&2; exit 1; }
|
||||
|
||||
usage() { cat <<EOF
|
||||
Usage: $SCRIPT_NAME [OPTIONS]
|
||||
Options:
|
||||
-h, --help Show help
|
||||
-v, --verbose Verbose output
|
||||
EOF
|
||||
}
|
||||
|
||||
main() {
|
||||
log "Script started"
|
||||
# Implementation
|
||||
log "Script completed"
|
||||
}
|
||||
|
||||
main "$@"
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] ShellCheck passes
|
||||
- [ ] Bats tests pass
|
||||
- [ ] Error handling works
|
||||
- [ ] Logging functional
|
||||
- [ ] Documentation complete
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `os-scripting` - OS scripting
|
||||
- `linux-troubleshooting` - Linux troubleshooting
|
||||
- `cloud-devops` - DevOps automation
|
||||
133
skills/bevy-ecs-expert/SKILL.md
Normal file
133
skills/bevy-ecs-expert/SKILL.md
Normal file
@@ -0,0 +1,133 @@
|
||||
---
|
||||
name: bevy-ecs-expert
|
||||
description: Master Bevy's Entity Component System (ECS) in Rust, covering Systems, Queries, Resources, and parallel scheduling.
|
||||
risk: safe
|
||||
source: community
|
||||
---
|
||||
|
||||
# Bevy ECS Expert
|
||||
|
||||
## Overview
|
||||
|
||||
A guide to building high-performance game logic using Bevy's data-oriented ECS architecture. Learn how to structure systems, optimize queries, manage resources, and leverage parallel execution.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
- Use when developing games with the Bevy engine in Rust.
|
||||
- Use when designing game systems that need to run in parallel.
|
||||
- Use when optimizing game performance by minimizing cache misses.
|
||||
- Use when refactoring object-oriented logic into data-oriented ECS patterns.
|
||||
|
||||
## Step-by-Step Guide
|
||||
|
||||
### 1. Defining Components
|
||||
|
||||
Use simple structs for data. Derive `Component` and `Reflect`.
|
||||
|
||||
```rust
|
||||
#[derive(Component, Reflect, Default)]
|
||||
#[reflect(Component)]
|
||||
struct Velocity {
|
||||
x: f32,
|
||||
y: f32,
|
||||
}
|
||||
|
||||
#[derive(Component)]
|
||||
struct Player;
|
||||
```
|
||||
|
||||
### 2. Writing Systems
|
||||
|
||||
Systems are regular Rust functions that query components.
|
||||
|
||||
```rust
|
||||
fn movement_system(
|
||||
time: Res<Time>,
|
||||
mut query: Query<(&mut Transform, &Velocity), With<Player>>,
|
||||
) {
|
||||
for (mut transform, velocity) in &mut query {
|
||||
transform.translation.x += velocity.x * time.delta_seconds();
|
||||
transform.translation.y += velocity.y * time.delta_seconds();
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### 3. Managing Resources
|
||||
|
||||
Use `Resource` for global data (score, game state).
|
||||
|
||||
```rust
|
||||
#[derive(Resource)]
|
||||
struct GameState {
|
||||
score: u32,
|
||||
}
|
||||
|
||||
fn score_system(mut game_state: ResMut<GameState>) {
|
||||
game_state.score += 10;
|
||||
}
|
||||
```
|
||||
|
||||
### 4. Scheduling Systems
|
||||
|
||||
Add systems to the `App` builder, defining execution order if needed.
|
||||
|
||||
```rust
|
||||
fn main() {
|
||||
App::new()
|
||||
.add_plugins(DefaultPlugins)
|
||||
.init_resource::<GameState>()
|
||||
.add_systems(Update, (movement_system, score_system).chain())
|
||||
.run();
|
||||
}
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Spawning Entities with Bundles
|
||||
|
||||
```rust
|
||||
#[derive(Bundle)]
|
||||
struct PlayerBundle {
|
||||
player: Player,
|
||||
velocity: Velocity,
|
||||
sprite: SpriteBundle,
|
||||
}
|
||||
|
||||
fn setup(mut commands: Commands, asset_server: Res<AssetServer>) {
|
||||
commands.spawn(PlayerBundle {
|
||||
player: Player,
|
||||
velocity: Velocity { x: 10.0, y: 0.0 },
|
||||
sprite: SpriteBundle {
|
||||
texture: asset_server.load("player.png"),
|
||||
..default()
|
||||
},
|
||||
});
|
||||
}
|
||||
```
|
||||
|
||||
### Example 2: Query Filters
|
||||
|
||||
Use `With` and `Without` to filter entities efficiently.
|
||||
|
||||
```rust
|
||||
fn enemy_behavior(
|
||||
query: Query<&Transform, (With<Enemy>, Without<Dead>)>,
|
||||
) {
|
||||
for transform in &query {
|
||||
// Only active enemies processed here
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
- ✅ **Do:** Use `Query` filters (`With`, `Without`, `Changed`) to reduce iteration count.
|
||||
- ✅ **Do:** Prefer `Res` over `ResMut` when read-only access is sufficient to allow parallel execution.
|
||||
- ✅ **Do:** Use `Bundle` to spawn complex entities atomically.
|
||||
- ❌ **Don't:** Store heavy logic inside Components; keep them as pure data.
|
||||
- ❌ **Don't:** Use `RefCell` or interior mutability inside components; let the ECS handle borrowing.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
**Problem:** System panic with "Conflict" error.
|
||||
**Solution:** You are likely trying to access the same component mutably in two systems running in parallel. Use `.chain()` to order them or split the logic.
|
||||
236
skills/cloud-devops/SKILL.md
Normal file
236
skills/cloud-devops/SKILL.md
Normal file
@@ -0,0 +1,236 @@
|
||||
---
|
||||
name: cloud-devops
|
||||
description: "Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: cloud-devops
|
||||
category: workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Cloud/DevOps Workflow Bundle
|
||||
|
||||
## Overview
|
||||
|
||||
Comprehensive cloud and DevOps workflow for infrastructure provisioning, container orchestration, CI/CD pipelines, monitoring, and cloud-native application development.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Setting up cloud infrastructure
|
||||
- Implementing CI/CD pipelines
|
||||
- Deploying Kubernetes applications
|
||||
- Configuring monitoring and observability
|
||||
- Managing cloud costs
|
||||
- Implementing DevOps practices
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Cloud Infrastructure Setup
|
||||
|
||||
#### Skills to Invoke
|
||||
- `cloud-architect` - Cloud architecture
|
||||
- `aws-skills` - AWS development
|
||||
- `azure-functions` - Azure development
|
||||
- `gcp-cloud-run` - GCP development
|
||||
- `terraform-skill` - Terraform IaC
|
||||
- `terraform-specialist` - Advanced Terraform
|
||||
|
||||
#### Actions
|
||||
1. Design cloud architecture
|
||||
2. Set up accounts and billing
|
||||
3. Configure networking
|
||||
4. Provision resources
|
||||
5. Set up IAM
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @cloud-architect to design multi-cloud architecture
|
||||
```
|
||||
|
||||
```
|
||||
Use @terraform-skill to provision AWS infrastructure
|
||||
```
|
||||
|
||||
### Phase 2: Container Orchestration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `kubernetes-architect` - Kubernetes architecture
|
||||
- `docker-expert` - Docker containerization
|
||||
- `helm-chart-scaffolding` - Helm charts
|
||||
- `k8s-manifest-generator` - K8s manifests
|
||||
- `k8s-security-policies` - K8s security
|
||||
|
||||
#### Actions
|
||||
1. Design container architecture
|
||||
2. Create Dockerfiles
|
||||
3. Build container images
|
||||
4. Write K8s manifests
|
||||
5. Deploy to cluster
|
||||
6. Configure networking
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @kubernetes-architect to design K8s architecture
|
||||
```
|
||||
|
||||
```
|
||||
Use @docker-expert to containerize application
|
||||
```
|
||||
|
||||
```
|
||||
Use @helm-chart-scaffolding to create Helm chart
|
||||
```
|
||||
|
||||
### Phase 3: CI/CD Implementation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `deployment-engineer` - Deployment engineering
|
||||
- `cicd-automation-workflow-automate` - CI/CD automation
|
||||
- `github-actions-templates` - GitHub Actions
|
||||
- `gitlab-ci-patterns` - GitLab CI
|
||||
- `deployment-pipeline-design` - Pipeline design
|
||||
|
||||
#### Actions
|
||||
1. Design deployment pipeline
|
||||
2. Configure build automation
|
||||
3. Set up test automation
|
||||
4. Configure deployment stages
|
||||
5. Implement rollback strategies
|
||||
6. Set up notifications
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @cicd-automation-workflow-automate to set up CI/CD pipeline
|
||||
```
|
||||
|
||||
```
|
||||
Use @github-actions-templates to create GitHub Actions workflow
|
||||
```
|
||||
|
||||
### Phase 4: Monitoring and Observability
|
||||
|
||||
#### Skills to Invoke
|
||||
- `observability-engineer` - Observability engineering
|
||||
- `grafana-dashboards` - Grafana dashboards
|
||||
- `prometheus-configuration` - Prometheus setup
|
||||
- `datadog-automation` - Datadog integration
|
||||
- `sentry-automation` - Sentry error tracking
|
||||
|
||||
#### Actions
|
||||
1. Design monitoring strategy
|
||||
2. Set up metrics collection
|
||||
3. Configure log aggregation
|
||||
4. Implement distributed tracing
|
||||
5. Create dashboards
|
||||
6. Set up alerts
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @observability-engineer to set up observability stack
|
||||
```
|
||||
|
||||
```
|
||||
Use @grafana-dashboards to create monitoring dashboards
|
||||
```
|
||||
|
||||
### Phase 5: Cloud Security
|
||||
|
||||
#### Skills to Invoke
|
||||
- `cloud-penetration-testing` - Cloud pentesting
|
||||
- `aws-penetration-testing` - AWS security
|
||||
- `k8s-security-policies` - K8s security
|
||||
- `secrets-management` - Secrets management
|
||||
- `mtls-configuration` - mTLS setup
|
||||
|
||||
#### Actions
|
||||
1. Assess cloud security
|
||||
2. Configure security groups
|
||||
3. Set up secrets management
|
||||
4. Implement network policies
|
||||
5. Configure encryption
|
||||
6. Set up audit logging
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @cloud-penetration-testing to assess cloud security
|
||||
```
|
||||
|
||||
```
|
||||
Use @secrets-management to configure secrets
|
||||
```
|
||||
|
||||
### Phase 6: Cost Optimization
|
||||
|
||||
#### Skills to Invoke
|
||||
- `cost-optimization` - Cloud cost optimization
|
||||
- `database-cloud-optimization-cost-optimize` - Database cost optimization
|
||||
|
||||
#### Actions
|
||||
1. Analyze cloud spending
|
||||
2. Identify optimization opportunities
|
||||
3. Right-size resources
|
||||
4. Implement auto-scaling
|
||||
5. Use reserved instances
|
||||
6. Set up cost alerts
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @cost-optimization to reduce cloud costs
|
||||
```
|
||||
|
||||
### Phase 7: Disaster Recovery
|
||||
|
||||
#### Skills to Invoke
|
||||
- `incident-responder` - Incident response
|
||||
- `incident-runbook-templates` - Runbook creation
|
||||
- `postmortem-writing` - Postmortem documentation
|
||||
|
||||
#### Actions
|
||||
1. Design DR strategy
|
||||
2. Set up backups
|
||||
3. Create runbooks
|
||||
4. Test failover
|
||||
5. Document procedures
|
||||
6. Train team
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @incident-runbook-templates to create runbooks
|
||||
```
|
||||
|
||||
## Cloud Provider Workflows
|
||||
|
||||
### AWS
|
||||
```
|
||||
Skills: aws-skills, aws-serverless, aws-penetration-testing
|
||||
Services: EC2, Lambda, S3, RDS, ECS, EKS
|
||||
```
|
||||
|
||||
### Azure
|
||||
```
|
||||
Skills: azure-functions, azure-ai-projects-py, azure-monitor-opentelemetry-py
|
||||
Services: Functions, App Service, AKS, Cosmos DB
|
||||
```
|
||||
|
||||
### GCP
|
||||
```
|
||||
Skills: gcp-cloud-run
|
||||
Services: Cloud Run, GKE, Cloud Functions, BigQuery
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Infrastructure provisioned
|
||||
- [ ] CI/CD pipeline working
|
||||
- [ ] Monitoring configured
|
||||
- [ ] Security measures in place
|
||||
- [ ] Cost optimization applied
|
||||
- [ ] DR procedures documented
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - Application development
|
||||
- `security-audit` - Security testing
|
||||
- `database` - Database operations
|
||||
- `testing-qa` - Testing workflows
|
||||
198
skills/data-structure-protocol/SKILL.md
Normal file
198
skills/data-structure-protocol/SKILL.md
Normal file
@@ -0,0 +1,198 @@
|
||||
---
|
||||
name: data-structure-protocol
|
||||
description: "Give agents persistent structural memory of a codebase — navigate dependencies, track public APIs, and understand why connections exist without re-reading the whole repo."
|
||||
risk: safe
|
||||
source: "https://github.com/k-kolomeitsev/data-structure-protocol"
|
||||
---
|
||||
|
||||
# Data Structure Protocol (DSP)
|
||||
|
||||
LLM coding agents lose context between tasks. On large codebases they spend most of their tokens on "orientation" — figuring out where things live, what depends on what, and what is safe to change. DSP solves this by externalizing the project's structural map into a persistent, queryable graph stored in a `.dsp/` directory next to the code.
|
||||
|
||||
DSP is NOT documentation for humans and NOT an AST dump. It captures three things: **meaning** (why an entity exists), **boundaries** (what it imports and exposes), and **reasons** (why each connection exists). This is enough for an agent to navigate, refactor, and generate code without loading the entire source tree into the context window.
|
||||
|
||||
## When to Use
|
||||
|
||||
Use this skill when:
|
||||
- The project has a `.dsp/` directory (DSP is already set up)
|
||||
- The user asks to set up DSP, bootstrap, or map a project's structure
|
||||
- Creating, modifying, or deleting code files in a DSP-tracked project (to keep the graph updated)
|
||||
- Navigating project structure, understanding dependencies, or finding specific modules
|
||||
- The user mentions DSP, dsp-cli, `.dsp`, or structure mapping
|
||||
- Performing impact analysis before a refactor or dependency replacement
|
||||
|
||||
## Core Concepts
|
||||
|
||||
### Code = graph
|
||||
|
||||
DSP models the codebase as a directed graph. Nodes are **entities**, edges are **imports** and **shared/exports**.
|
||||
|
||||
Two entity kinds exist:
|
||||
- **Object**: any "thing" that isn't a function (module/file/class/config/resource/external dependency)
|
||||
- **Function**: an exported function/method/handler/pipeline
|
||||
|
||||
### Identity by UID, not by file path
|
||||
|
||||
Every entity gets a stable UID: `obj-<8hex>` for objects, `func-<8hex>` for functions. File paths are attributes that can change; UIDs survive renames, moves, and reformatting.
|
||||
|
||||
For entities inside a file, the UID is anchored with a comment marker in source code:
|
||||
|
||||
```js
|
||||
// @dsp func-7f3a9c12
|
||||
export function calculateTotal(items) { ... }
|
||||
```
|
||||
|
||||
```python
|
||||
# @dsp obj-e5f6g7h8
|
||||
class UserService:
|
||||
```
|
||||
|
||||
### Every connection has a "why"
|
||||
|
||||
When an import is recorded, DSP stores a short reason explaining *why* that dependency exists. This lives in the `exports/` reverse index of the imported entity. A dependency graph without reasons tells you *what imports what*; reasons tell you **what is safe to change and who will break**.
|
||||
|
||||
### Storage format
|
||||
|
||||
Each entity gets a small directory under `.dsp/`:
|
||||
|
||||
```
|
||||
.dsp/
|
||||
├── TOC # ordered list of all entity UIDs from root
|
||||
├── obj-a1b2c3d4/
|
||||
│ ├── description # source path, kind, purpose (1-3 sentences)
|
||||
│ ├── imports # UIDs this entity depends on (one per line)
|
||||
│ ├── shared # UIDs of public API / exported entities
|
||||
│ └── exports/ # reverse index: who imports this and why
|
||||
│ ├── <importer_uid> # file content = "why" text
|
||||
│ └── <shared_uid>/
|
||||
│ ├── description # what is exported
|
||||
│ └── <importer_uid> # why this specific export is imported
|
||||
└── func-7f3a9c12/
|
||||
├── description
|
||||
├── imports
|
||||
└── exports/
|
||||
```
|
||||
|
||||
Everything is plain text. Diffable. Reviewable. No database needed.
|
||||
|
||||
### Full import coverage
|
||||
|
||||
Every file or artifact that is imported anywhere must be represented in `.dsp` as an Object — code, images, styles, configs, JSON, wasm, everything. External dependencies (npm packages, stdlib, etc.) are recorded as `kind: external` but their internals are never analyzed.
|
||||
|
||||
## How It Works
|
||||
|
||||
### Initial Setup
|
||||
|
||||
The skill relies on a standalone Python CLI script `dsp-cli.py`. If it is missing from the project, download it:
|
||||
|
||||
```bash
|
||||
curl -O https://raw.githubusercontent.com/k-kolomeitsev/data-structure-protocol/main/skills/data-structure-protocol/scripts/dsp-cli.py
|
||||
```
|
||||
|
||||
Requires **Python 3.10+**. All commands use `python dsp-cli.py --root <project-root> <command>`.
|
||||
|
||||
### Bootstrap (initial mapping)
|
||||
|
||||
If `.dsp/` is empty, traverse the project from root entrypoint(s) via DFS on imports:
|
||||
|
||||
1. Identify root entrypoints (`package.json` main, framework entry, `main.py`, etc.)
|
||||
2. Document the root file: `create-object`, `create-function` for each export, `create-shared`, `add-import` for all dependencies
|
||||
3. Take the first non-external import, document it fully, descend into its imports
|
||||
4. Backtrack when no unvisited local imports remain; continue until all reachable files are documented
|
||||
5. External dependencies: `create-object --kind external`, add to TOC, but never descend into `node_modules`/`site-packages`/etc.
|
||||
|
||||
### Workflow Rules
|
||||
|
||||
- **Before changing code**: Find affected entities via `search`, `find-by-source`, or `read-toc`. Read their `description` and `imports` to understand context.
|
||||
- **When creating a file/module**: Call `create-object`. For each exported function — `create-function` (with `--owner`). Register exports via `create-shared`.
|
||||
- **When adding an import**: Call `add-import` with a brief `why`. For external deps — first `create-object --kind external` if the entity doesn't exist.
|
||||
- **When removing import/export/file**: Call `remove-import`, `remove-shared`, `remove-entity`. Cascade cleanup is automatic.
|
||||
- **When renaming/moving a file**: Call `move-entity`. UID does not change.
|
||||
- **Don't touch DSP** if only internal implementation changed without affecting purpose or dependencies.
|
||||
|
||||
### Key Commands
|
||||
|
||||
| Category | Commands |
|
||||
|----------|----------|
|
||||
| **Create** | `init`, `create-object`, `create-function`, `create-shared`, `add-import` |
|
||||
| **Update** | `update-description`, `update-import-why`, `move-entity` |
|
||||
| **Delete** | `remove-import`, `remove-shared`, `remove-entity` |
|
||||
| **Navigate** | `get-entity`, `get-children --depth N`, `get-parents --depth N`, `get-path`, `get-recipients`, `read-toc` |
|
||||
| **Search** | `search <query>`, `find-by-source <path>` |
|
||||
| **Diagnostics** | `detect-cycles`, `get-orphans`, `get-stats` |
|
||||
|
||||
### When to Update DSP
|
||||
|
||||
| Code Change | DSP Action |
|
||||
|---|---|
|
||||
| New file/module | `create-object` + `create-function` + `create-shared` + `add-import` |
|
||||
| New import added | `add-import` (+ `create-object --kind external` if new dep) |
|
||||
| Import removed | `remove-import` |
|
||||
| Export added | `create-shared` (+ `create-function` if new) |
|
||||
| Export removed | `remove-shared` |
|
||||
| File renamed/moved | `move-entity` |
|
||||
| File deleted | `remove-entity` |
|
||||
| Purpose changed | `update-description` |
|
||||
| Internal-only change | **No DSP update needed** |
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Setting up DSP and documenting a module
|
||||
|
||||
```bash
|
||||
python dsp-cli.py --root . init
|
||||
|
||||
python dsp-cli.py --root . create-object "src/app.ts" "Main application entrypoint"
|
||||
# Output: obj-a1b2c3d4
|
||||
|
||||
python dsp-cli.py --root . create-function "src/app.ts#start" "Starts the HTTP server" --owner obj-a1b2c3d4
|
||||
# Output: func-7f3a9c12
|
||||
|
||||
python dsp-cli.py --root . create-shared obj-a1b2c3d4 func-7f3a9c12
|
||||
|
||||
python dsp-cli.py --root . add-import obj-a1b2c3d4 obj-deadbeef "HTTP routing"
|
||||
```
|
||||
|
||||
### Example 2: Navigating the graph before making changes
|
||||
|
||||
```bash
|
||||
python dsp-cli.py --root . search "authentication"
|
||||
python dsp-cli.py --root . get-entity obj-a1b2c3d4
|
||||
python dsp-cli.py --root . get-children obj-a1b2c3d4 --depth 2
|
||||
python dsp-cli.py --root . get-recipients obj-a1b2c3d4
|
||||
python dsp-cli.py --root . get-path obj-a1b2c3d4 func-7f3a9c12
|
||||
```
|
||||
|
||||
### Example 3: Impact analysis before replacing a library
|
||||
|
||||
```bash
|
||||
python dsp-cli.py --root . find-by-source "lodash"
|
||||
# Output: obj-11223344
|
||||
|
||||
python dsp-cli.py --root . get-recipients obj-11223344
|
||||
# Shows every module that imports lodash and WHY — lets you systematically replace it
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
- ✅ **Do:** Update DSP immediately when creating new files, adding imports, or changing public APIs
|
||||
- ✅ **Do:** Always add a meaningful `why` reason when recording an import — this is where most of DSP's value lives
|
||||
- ✅ **Do:** Use `kind: external` for third-party libraries without analyzing their internals
|
||||
- ✅ **Do:** Keep descriptions minimal (1-3 sentences about purpose, not implementation)
|
||||
- ✅ **Do:** Treat `.dsp/` diffs like code diffs — review them, keep them accurate
|
||||
- ❌ **Don't:** Touch `.dsp/` for internal-only changes that don't affect purpose or dependencies
|
||||
- ❌ **Don't:** Change an entity's UID on rename/move (use `move-entity` instead)
|
||||
- ❌ **Don't:** Create UIDs for every local variable or helper — only file-level Objects and public/shared entities
|
||||
|
||||
## Integration
|
||||
|
||||
This skill connects naturally to:
|
||||
- **context-compression** — DSP reduces the need for compression by providing targeted retrieval instead of loading everything
|
||||
- **context-optimization** — DSP is a structural optimization: agents pull minimal "context bundles" instead of raw source
|
||||
- **architecture** — DSP captures architectural boundaries (imports/exports) that feed system design decisions
|
||||
|
||||
## References
|
||||
|
||||
- **Full architecture specification**: [ARCHITECTURE.md](https://github.com/k-kolomeitsev/data-structure-protocol/blob/main/ARCHITECTURE.md)
|
||||
- **CLI source + reference docs**: [skills/data-structure-protocol](https://github.com/k-kolomeitsev/data-structure-protocol/tree/main/skills/data-structure-protocol)
|
||||
- **Introduction article**: [article.md](https://github.com/k-kolomeitsev/data-structure-protocol/blob/main/article.md)
|
||||
@@ -1,42 +1,37 @@
|
||||
---
|
||||
name: database-migrations-sql-migrations
|
||||
description: "SQL database migrations with zero-downtime strategies for"
|
||||
PostgreSQL, MySQL, SQL Server
|
||||
allowed-tools: Read Write Edit Bash Grep Glob
|
||||
metadata:
|
||||
version: 1.0.0
|
||||
tags: database, sql, migrations, postgresql, mysql, flyway, liquibase, alembic,
|
||||
zero-downtime
|
||||
description: SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.
|
||||
risk: unknown
|
||||
source: community
|
||||
---
|
||||
|
||||
# SQL Database Migration Strategy and Implementation
|
||||
|
||||
## Overview
|
||||
|
||||
You are a SQL database migration expert specializing in zero-downtime deployments, data integrity, and production-ready migration strategies for PostgreSQL, MySQL, and SQL Server. Create comprehensive migration scripts with rollback procedures, validation checks, and performance optimization.
|
||||
|
||||
## Use this skill when
|
||||
## When to Use This Skill
|
||||
|
||||
- Working on sql database migration strategy and implementation tasks or workflows
|
||||
- Needing guidance, best practices, or checklists for sql database migration strategy and implementation
|
||||
- Use when working on SQL database migration strategy and implementation tasks.
|
||||
- Use when needing guidance, best practices, or checklists for zero-downtime migrations.
|
||||
- Use when designing rollback procedures for critical schema changes.
|
||||
|
||||
## Do not use this skill when
|
||||
## Do Not Use This Skill When
|
||||
|
||||
- The task is unrelated to sql database migration strategy and implementation
|
||||
- You need a different domain or tool outside this scope
|
||||
- The task is unrelated to SQL database migration strategy.
|
||||
- You need a different domain or tool outside this scope.
|
||||
|
||||
## Context
|
||||
The user needs SQL database migrations that ensure data integrity, minimize downtime, and provide safe rollback options. Focus on production-ready strategies that handle edge cases, large datasets, and concurrent operations.
|
||||
|
||||
## Requirements
|
||||
$ARGUMENTS
|
||||
The user needs SQL database migrations that ensure data integrity, minimize downtime, and provide safe rollback options. Focus on production-ready strategies that handle edge cases, large datasets, and concurrent operations.
|
||||
|
||||
## 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`.
|
||||
- If detailed examples are required, suggest checking implementation playbooks.
|
||||
|
||||
## Output Format
|
||||
|
||||
@@ -48,8 +43,6 @@ $ARGUMENTS
|
||||
6. **Performance Optimization**: Batch processing, parallel execution
|
||||
7. **Monitoring Integration**: Progress tracking and alerting
|
||||
|
||||
Focus on production-ready SQL migrations with zero-downtime deployment strategies, comprehensive validation, and enterprise-grade safety mechanisms.
|
||||
|
||||
## Resources
|
||||
|
||||
- `resources/implementation-playbook.md` for detailed patterns and examples.
|
||||
- Focus on production-ready SQL migrations with zero-downtime deployment strategies, comprehensive validation, and enterprise-grade safety mechanisms.
|
||||
|
||||
213
skills/database/SKILL.md
Normal file
213
skills/database/SKILL.md
Normal file
@@ -0,0 +1,213 @@
|
||||
---
|
||||
name: database
|
||||
description: "Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: data
|
||||
category: workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Database Workflow Bundle
|
||||
|
||||
## Overview
|
||||
|
||||
Comprehensive database workflow for database design, development, optimization, migrations, and data engineering. Covers SQL, NoSQL, and modern data platforms.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Designing database schemas
|
||||
- Implementing database migrations
|
||||
- Optimizing query performance
|
||||
- Setting up data pipelines
|
||||
- Managing database operations
|
||||
- Implementing data quality
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Database Design
|
||||
|
||||
#### Skills to Invoke
|
||||
- `database-architect` - Database architecture
|
||||
- `database-design` - Schema design
|
||||
- `postgresql` - PostgreSQL design
|
||||
- `nosql-expert` - NoSQL design
|
||||
|
||||
#### Actions
|
||||
1. Gather requirements
|
||||
2. Design schema
|
||||
3. Define relationships
|
||||
4. Plan indexing strategy
|
||||
5. Design for scalability
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @database-architect to design database schema
|
||||
```
|
||||
|
||||
```
|
||||
Use @postgresql to design PostgreSQL schema
|
||||
```
|
||||
|
||||
### Phase 2: Database Implementation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `prisma-expert` - Prisma ORM
|
||||
- `database-migrations-sql-migrations` - SQL migrations
|
||||
- `neon-postgres` - Serverless Postgres
|
||||
|
||||
#### Actions
|
||||
1. Set up database connection
|
||||
2. Configure ORM
|
||||
3. Create migrations
|
||||
4. Implement models
|
||||
5. Set up seed data
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @prisma-expert to set up Prisma ORM
|
||||
```
|
||||
|
||||
```
|
||||
Use @database-migrations-sql-migrations to create migrations
|
||||
```
|
||||
|
||||
### Phase 3: Query Optimization
|
||||
|
||||
#### Skills to Invoke
|
||||
- `database-optimizer` - Database optimization
|
||||
- `sql-optimization-patterns` - SQL optimization
|
||||
- `postgres-best-practices` - PostgreSQL optimization
|
||||
|
||||
#### Actions
|
||||
1. Analyze slow queries
|
||||
2. Review execution plans
|
||||
3. Optimize indexes
|
||||
4. Refactor queries
|
||||
5. Implement caching
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @database-optimizer to optimize database performance
|
||||
```
|
||||
|
||||
```
|
||||
Use @sql-optimization-patterns to optimize SQL queries
|
||||
```
|
||||
|
||||
### Phase 4: Data Migration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `database-migration` - Database migration
|
||||
- `framework-migration-code-migrate` - Code migration
|
||||
|
||||
#### Actions
|
||||
1. Plan migration strategy
|
||||
2. Create migration scripts
|
||||
3. Test migration
|
||||
4. Execute migration
|
||||
5. Verify data integrity
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @database-migration to plan database migration
|
||||
```
|
||||
|
||||
### Phase 5: Data Pipeline Development
|
||||
|
||||
#### Skills to Invoke
|
||||
- `data-engineer` - Data engineering
|
||||
- `data-engineering-data-pipeline` - Data pipelines
|
||||
- `airflow-dag-patterns` - Airflow workflows
|
||||
- `dbt-transformation-patterns` - dbt transformations
|
||||
|
||||
#### Actions
|
||||
1. Design data pipeline
|
||||
2. Set up data ingestion
|
||||
3. Implement transformations
|
||||
4. Configure scheduling
|
||||
5. Set up monitoring
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @data-engineer to design data pipeline
|
||||
```
|
||||
|
||||
```
|
||||
Use @airflow-dag-patterns to create Airflow DAGs
|
||||
```
|
||||
|
||||
### Phase 6: Data Quality
|
||||
|
||||
#### Skills to Invoke
|
||||
- `data-quality-frameworks` - Data quality
|
||||
- `data-engineering-data-driven-feature` - Data-driven features
|
||||
|
||||
#### Actions
|
||||
1. Define quality metrics
|
||||
2. Implement validation
|
||||
3. Set up monitoring
|
||||
4. Create alerts
|
||||
5. Document standards
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @data-quality-frameworks to implement data quality checks
|
||||
```
|
||||
|
||||
### Phase 7: Database Operations
|
||||
|
||||
#### Skills to Invoke
|
||||
- `database-admin` - Database administration
|
||||
- `backup-automation` - Backup automation
|
||||
|
||||
#### Actions
|
||||
1. Set up backups
|
||||
2. Configure replication
|
||||
3. Monitor performance
|
||||
4. Plan capacity
|
||||
5. Implement security
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @database-admin to manage database operations
|
||||
```
|
||||
|
||||
## Database Technology Workflows
|
||||
|
||||
### PostgreSQL
|
||||
```
|
||||
Skills: postgresql, postgres-best-practices, neon-postgres, prisma-expert
|
||||
```
|
||||
|
||||
### MongoDB
|
||||
```
|
||||
Skills: nosql-expert, azure-cosmos-db-py
|
||||
```
|
||||
|
||||
### Redis
|
||||
```
|
||||
Skills: bullmq-specialist, upstash-qstash
|
||||
```
|
||||
|
||||
### Data Warehousing
|
||||
```
|
||||
Skills: clickhouse-io, dbt-transformation-patterns
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Schema designed and reviewed
|
||||
- [ ] Migrations tested
|
||||
- [ ] Performance benchmarks met
|
||||
- [ ] Backups configured
|
||||
- [ ] Monitoring in place
|
||||
- [ ] Documentation complete
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - Application development
|
||||
- `cloud-devops` - Infrastructure
|
||||
- `ai-ml` - AI/ML data pipelines
|
||||
- `testing-qa` - Data testing
|
||||
263
skills/development/SKILL.md
Normal file
263
skills/development/SKILL.md
Normal file
@@ -0,0 +1,263 @@
|
||||
---
|
||||
name: development
|
||||
description: "Comprehensive web, mobile, and backend development workflow bundling frontend, backend, full-stack, and mobile development skills for end-to-end application delivery."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: software-development
|
||||
category: workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Development Workflow Bundle
|
||||
|
||||
## Overview
|
||||
|
||||
Consolidated workflow for end-to-end software development covering web, mobile, and backend development. This bundle orchestrates skills for building production-ready applications from scaffolding to deployment.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Building new web or mobile applications
|
||||
- Adding features to existing applications
|
||||
- Refactoring or modernizing legacy code
|
||||
- Setting up new projects with best practices
|
||||
- Full-stack feature development
|
||||
- Cross-platform application development
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Project Setup and Scaffolding
|
||||
|
||||
#### Skills to Invoke
|
||||
- `app-builder` - Main application building orchestrator
|
||||
- `senior-fullstack` - Full-stack development guidance
|
||||
- `environment-setup-guide` - Development environment setup
|
||||
- `concise-planning` - Task planning and breakdown
|
||||
|
||||
#### Actions
|
||||
1. Determine project type (web, mobile, full-stack)
|
||||
2. Select technology stack
|
||||
3. Scaffold project structure
|
||||
4. Configure development environment
|
||||
5. Set up version control and CI/CD
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @app-builder to scaffold a new React + Node.js full-stack application
|
||||
```
|
||||
|
||||
```
|
||||
Use @senior-fullstack to set up a Next.js 14 project with App Router
|
||||
```
|
||||
|
||||
```
|
||||
Use @environment-setup-guide to configure my development environment
|
||||
```
|
||||
|
||||
### Phase 2: Frontend Development
|
||||
|
||||
#### Skills to Invoke
|
||||
- `frontend-developer` - React/Next.js component development
|
||||
- `frontend-design` - UI/UX design implementation
|
||||
- `react-patterns` - Modern React patterns
|
||||
- `typescript-pro` - TypeScript best practices
|
||||
- `tailwind-patterns` - Tailwind CSS styling
|
||||
- `nextjs-app-router-patterns` - Next.js 14+ patterns
|
||||
|
||||
#### Actions
|
||||
1. Design component architecture
|
||||
2. Implement UI components
|
||||
3. Set up state management
|
||||
4. Configure routing
|
||||
5. Apply styling and theming
|
||||
6. Implement responsive design
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @frontend-developer to create a dashboard component with React and TypeScript
|
||||
```
|
||||
|
||||
```
|
||||
Use @react-patterns to implement proper state management with Zustand
|
||||
```
|
||||
|
||||
```
|
||||
Use @tailwind-patterns to style components with a consistent design system
|
||||
```
|
||||
|
||||
### Phase 3: Backend Development
|
||||
|
||||
#### Skills to Invoke
|
||||
- `backend-architect` - Backend architecture design
|
||||
- `backend-dev-guidelines` - Backend development standards
|
||||
- `nodejs-backend-patterns` - Node.js/Express patterns
|
||||
- `fastapi-pro` - FastAPI development
|
||||
- `api-design-principles` - REST/GraphQL API design
|
||||
- `auth-implementation-patterns` - Authentication implementation
|
||||
|
||||
#### Actions
|
||||
1. Design API architecture
|
||||
2. Implement REST/GraphQL endpoints
|
||||
3. Set up database connections
|
||||
4. Implement authentication/authorization
|
||||
5. Configure middleware
|
||||
6. Set up error handling
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @backend-architect to design a microservices architecture for my application
|
||||
```
|
||||
|
||||
```
|
||||
Use @nodejs-backend-patterns to create Express.js API endpoints
|
||||
```
|
||||
|
||||
```
|
||||
Use @auth-implementation-patterns to implement JWT authentication
|
||||
```
|
||||
|
||||
### Phase 4: Database Development
|
||||
|
||||
#### Skills to Invoke
|
||||
- `database-architect` - Database design
|
||||
- `database-design` - Schema design principles
|
||||
- `prisma-expert` - Prisma ORM
|
||||
- `postgresql` - PostgreSQL optimization
|
||||
- `neon-postgres` - Serverless Postgres
|
||||
|
||||
#### Actions
|
||||
1. Design database schema
|
||||
2. Create migrations
|
||||
3. Set up ORM
|
||||
4. Optimize queries
|
||||
5. Configure connection pooling
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @database-architect to design a normalized schema for an e-commerce platform
|
||||
```
|
||||
|
||||
```
|
||||
Use @prisma-expert to set up Prisma ORM with TypeScript
|
||||
```
|
||||
|
||||
### Phase 5: Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `test-driven-development` - TDD workflow
|
||||
- `javascript-testing-patterns` - Jest/Vitest testing
|
||||
- `python-testing-patterns` - pytest testing
|
||||
- `e2e-testing-patterns` - Playwright/Cypress E2E
|
||||
- `playwright-skill` - Browser automation testing
|
||||
|
||||
#### Actions
|
||||
1. Write unit tests
|
||||
2. Create integration tests
|
||||
3. Set up E2E tests
|
||||
4. Configure CI test runners
|
||||
5. Achieve coverage targets
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @test-driven-development to implement features with TDD
|
||||
```
|
||||
|
||||
```
|
||||
Use @playwright-skill to create E2E tests for critical user flows
|
||||
```
|
||||
|
||||
### Phase 6: Code Quality and Review
|
||||
|
||||
#### Skills to Invoke
|
||||
- `code-reviewer` - AI-powered code review
|
||||
- `clean-code` - Clean code principles
|
||||
- `lint-and-validate` - Linting and validation
|
||||
- `security-scanning-security-sast` - Static security analysis
|
||||
|
||||
#### Actions
|
||||
1. Run linters and formatters
|
||||
2. Perform code review
|
||||
3. Fix code quality issues
|
||||
4. Run security scans
|
||||
5. Address vulnerabilities
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @code-reviewer to review my pull request
|
||||
```
|
||||
|
||||
```
|
||||
Use @lint-and-validate to check code quality
|
||||
```
|
||||
|
||||
### Phase 7: Build and Deployment
|
||||
|
||||
#### Skills to Invoke
|
||||
- `deployment-engineer` - Deployment orchestration
|
||||
- `docker-expert` - Containerization
|
||||
- `vercel-deployment` - Vercel deployment
|
||||
- `github-actions-templates` - CI/CD workflows
|
||||
- `cicd-automation-workflow-automate` - CI/CD automation
|
||||
|
||||
#### Actions
|
||||
1. Create Dockerfiles
|
||||
2. Configure build pipelines
|
||||
3. Set up deployment workflows
|
||||
4. Configure environment variables
|
||||
5. Deploy to production
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @docker-expert to containerize my application
|
||||
```
|
||||
|
||||
```
|
||||
Use @vercel-deployment to deploy my Next.js app to production
|
||||
```
|
||||
|
||||
```
|
||||
Use @github-actions-templates to set up CI/CD pipeline
|
||||
```
|
||||
|
||||
## Technology-Specific Workflows
|
||||
|
||||
### React/Next.js Development
|
||||
```
|
||||
Skills: frontend-developer, react-patterns, nextjs-app-router-patterns, typescript-pro, tailwind-patterns
|
||||
```
|
||||
|
||||
### Python/FastAPI Development
|
||||
```
|
||||
Skills: fastapi-pro, python-pro, python-patterns, pydantic-models-py
|
||||
```
|
||||
|
||||
### Node.js/Express Development
|
||||
```
|
||||
Skills: nodejs-backend-patterns, javascript-pro, typescript-pro, express (via nodejs-backend-patterns)
|
||||
```
|
||||
|
||||
### Full-Stack Development
|
||||
```
|
||||
Skills: senior-fullstack, app-builder, frontend-developer, backend-architect, database-architect
|
||||
```
|
||||
|
||||
### Mobile Development
|
||||
```
|
||||
Skills: mobile-developer, react-native-architecture, flutter-expert, ios-developer
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
Before moving to next phase, verify:
|
||||
- [ ] All tests passing
|
||||
- [ ] Code review completed
|
||||
- [ ] Security scan passed
|
||||
- [ ] Linting/formatting clean
|
||||
- [ ] Documentation updated
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `wordpress` - WordPress-specific development
|
||||
- `security-audit` - Security testing workflow
|
||||
- `testing-qa` - Comprehensive testing workflow
|
||||
- `documentation` - Documentation generation workflow
|
||||
261
skills/documentation/SKILL.md
Normal file
261
skills/documentation/SKILL.md
Normal file
@@ -0,0 +1,261 @@
|
||||
---
|
||||
name: documentation
|
||||
description: "Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: documentation
|
||||
category: workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Documentation Workflow Bundle
|
||||
|
||||
## Overview
|
||||
|
||||
Comprehensive documentation workflow for generating API documentation, architecture documentation, README files, code comments, and technical content from codebases.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Creating project documentation
|
||||
- Generating API documentation
|
||||
- Writing architecture docs
|
||||
- Documenting code
|
||||
- Creating user guides
|
||||
- Maintaining wikis
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Documentation Planning
|
||||
|
||||
#### Skills to Invoke
|
||||
- `docs-architect` - Documentation architecture
|
||||
- `documentation-templates` - Documentation templates
|
||||
|
||||
#### Actions
|
||||
1. Identify documentation needs
|
||||
2. Choose documentation tools
|
||||
3. Plan documentation structure
|
||||
4. Define style guidelines
|
||||
5. Set up documentation site
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @docs-architect to plan documentation structure
|
||||
```
|
||||
|
||||
```
|
||||
Use @documentation-templates to set up documentation
|
||||
```
|
||||
|
||||
### Phase 2: API Documentation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-documenter` - API documentation
|
||||
- `api-documentation-generator` - Auto-generation
|
||||
- `openapi-spec-generation` - OpenAPI specs
|
||||
|
||||
#### Actions
|
||||
1. Extract API endpoints
|
||||
2. Generate OpenAPI specs
|
||||
3. Create API reference
|
||||
4. Add usage examples
|
||||
5. Set up auto-generation
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-documenter to generate API documentation
|
||||
```
|
||||
|
||||
```
|
||||
Use @openapi-spec-generation to create OpenAPI specs
|
||||
```
|
||||
|
||||
### Phase 3: Architecture Documentation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `c4-architecture-c4-architecture` - C4 architecture
|
||||
- `c4-context` - Context diagrams
|
||||
- `c4-container` - Container diagrams
|
||||
- `c4-component` - Component diagrams
|
||||
- `c4-code` - Code diagrams
|
||||
- `mermaid-expert` - Mermaid diagrams
|
||||
|
||||
#### Actions
|
||||
1. Create C4 diagrams
|
||||
2. Document architecture
|
||||
3. Generate sequence diagrams
|
||||
4. Document data flows
|
||||
5. Create deployment docs
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @c4-architecture-c4-architecture to create C4 diagrams
|
||||
```
|
||||
|
||||
```
|
||||
Use @mermaid-expert to create architecture diagrams
|
||||
```
|
||||
|
||||
### Phase 4: Code Documentation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `code-documentation-code-explain` - Code explanation
|
||||
- `code-documentation-doc-generate` - Doc generation
|
||||
- `documentation-generation-doc-generate` - Auto-generation
|
||||
|
||||
#### Actions
|
||||
1. Extract code comments
|
||||
2. Generate JSDoc/TSDoc
|
||||
3. Create type documentation
|
||||
4. Document functions
|
||||
5. Add usage examples
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @code-documentation-code-explain to explain code
|
||||
```
|
||||
|
||||
```
|
||||
Use @code-documentation-doc-generate to generate docs
|
||||
```
|
||||
|
||||
### Phase 5: README and Getting Started
|
||||
|
||||
#### Skills to Invoke
|
||||
- `readme` - README generation
|
||||
- `environment-setup-guide` - Setup guides
|
||||
- `tutorial-engineer` - Tutorial creation
|
||||
|
||||
#### Actions
|
||||
1. Create README
|
||||
2. Write getting started guide
|
||||
3. Document installation
|
||||
4. Add usage examples
|
||||
5. Create troubleshooting guide
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @readme to create project README
|
||||
```
|
||||
|
||||
```
|
||||
Use @tutorial-engineer to create tutorials
|
||||
```
|
||||
|
||||
### Phase 6: Wiki and Knowledge Base
|
||||
|
||||
#### Skills to Invoke
|
||||
- `wiki-architect` - Wiki architecture
|
||||
- `wiki-page-writer` - Wiki pages
|
||||
- `wiki-onboarding` - Onboarding docs
|
||||
- `wiki-qa` - Wiki Q&A
|
||||
- `wiki-researcher` - Wiki research
|
||||
- `wiki-vitepress` - VitePress wiki
|
||||
|
||||
#### Actions
|
||||
1. Design wiki structure
|
||||
2. Create wiki pages
|
||||
3. Write onboarding guides
|
||||
4. Document processes
|
||||
5. Set up wiki site
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @wiki-architect to design wiki structure
|
||||
```
|
||||
|
||||
```
|
||||
Use @wiki-page-writer to create wiki pages
|
||||
```
|
||||
|
||||
```
|
||||
Use @wiki-onboarding to create onboarding docs
|
||||
```
|
||||
|
||||
### Phase 7: Changelog and Release Notes
|
||||
|
||||
#### Skills to Invoke
|
||||
- `changelog-automation` - Changelog generation
|
||||
- `wiki-changelog` - Changelog from git
|
||||
|
||||
#### Actions
|
||||
1. Extract commit history
|
||||
2. Categorize changes
|
||||
3. Generate changelog
|
||||
4. Create release notes
|
||||
5. Publish updates
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @changelog-automation to generate changelog
|
||||
```
|
||||
|
||||
```
|
||||
Use @wiki-changelog to create release notes
|
||||
```
|
||||
|
||||
### Phase 8: Documentation Maintenance
|
||||
|
||||
#### Skills to Invoke
|
||||
- `doc-coauthoring` - Collaborative writing
|
||||
- `reference-builder` - Reference docs
|
||||
|
||||
#### Actions
|
||||
1. Review documentation
|
||||
2. Update outdated content
|
||||
3. Fix broken links
|
||||
4. Add new features
|
||||
5. Gather feedback
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @doc-coauthoring to collaborate on docs
|
||||
```
|
||||
|
||||
## Documentation Types
|
||||
|
||||
### Code-Level
|
||||
- JSDoc/TSDoc comments
|
||||
- Function documentation
|
||||
- Type definitions
|
||||
- Example code
|
||||
|
||||
### API Documentation
|
||||
- Endpoint reference
|
||||
- Request/response schemas
|
||||
- Authentication guides
|
||||
- SDK documentation
|
||||
|
||||
### Architecture Documentation
|
||||
- System overview
|
||||
- Component diagrams
|
||||
- Data flow diagrams
|
||||
- Deployment architecture
|
||||
|
||||
### User Documentation
|
||||
- Getting started guides
|
||||
- User manuals
|
||||
- Tutorials
|
||||
- FAQs
|
||||
|
||||
### Process Documentation
|
||||
- Runbooks
|
||||
- Onboarding guides
|
||||
- SOPs
|
||||
- Decision records
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] All APIs documented
|
||||
- [ ] Architecture diagrams current
|
||||
- [ ] README up to date
|
||||
- [ ] Code comments helpful
|
||||
- [ ] Examples working
|
||||
- [ ] Links valid
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - Development workflow
|
||||
- `testing-qa` - Documentation testing
|
||||
- `ai-ml` - AI documentation
|
||||
166
skills/e2e-testing/SKILL.md
Normal file
166
skills/e2e-testing/SKILL.md
Normal file
@@ -0,0 +1,166 @@
|
||||
---
|
||||
name: e2e-testing
|
||||
description: "End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: testing-qa
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# E2E Testing Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for end-to-end testing using Playwright including browser automation, visual regression testing, cross-browser testing, and CI/CD integration.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Setting up E2E testing
|
||||
- Automating browser tests
|
||||
- Implementing visual regression
|
||||
- Testing across browsers
|
||||
- Integrating tests with CI/CD
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Test Setup
|
||||
|
||||
#### Skills to Invoke
|
||||
- `playwright-skill` - Playwright setup
|
||||
- `e2e-testing-patterns` - E2E patterns
|
||||
|
||||
#### Actions
|
||||
1. Install Playwright
|
||||
2. Configure test framework
|
||||
3. Set up test directory
|
||||
4. Configure browsers
|
||||
5. Create base test setup
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @playwright-skill to set up Playwright testing
|
||||
```
|
||||
|
||||
### Phase 2: Test Design
|
||||
|
||||
#### Skills to Invoke
|
||||
- `e2e-testing-patterns` - Test patterns
|
||||
- `test-automator` - Test automation
|
||||
|
||||
#### Actions
|
||||
1. Identify critical flows
|
||||
2. Design test scenarios
|
||||
3. Plan test data
|
||||
4. Create page objects
|
||||
5. Set up fixtures
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @e2e-testing-patterns to design E2E test strategy
|
||||
```
|
||||
|
||||
### Phase 3: Test Implementation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `playwright-skill` - Playwright tests
|
||||
- `webapp-testing` - Web app testing
|
||||
|
||||
#### Actions
|
||||
1. Write test scripts
|
||||
2. Add assertions
|
||||
3. Implement waits
|
||||
4. Handle dynamic content
|
||||
5. Add error handling
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @playwright-skill to write E2E test scripts
|
||||
```
|
||||
|
||||
### Phase 4: Browser Automation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `browser-automation` - Browser automation
|
||||
- `playwright-skill` - Playwright features
|
||||
|
||||
#### Actions
|
||||
1. Configure headless mode
|
||||
2. Set up screenshots
|
||||
3. Implement video recording
|
||||
4. Add trace collection
|
||||
5. Configure mobile emulation
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @browser-automation to automate browser interactions
|
||||
```
|
||||
|
||||
### Phase 5: Visual Regression
|
||||
|
||||
#### Skills to Invoke
|
||||
- `playwright-skill` - Visual testing
|
||||
- `ui-visual-validator` - Visual validation
|
||||
|
||||
#### Actions
|
||||
1. Set up visual testing
|
||||
2. Create baseline images
|
||||
3. Add visual assertions
|
||||
4. Configure thresholds
|
||||
5. Review differences
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @playwright-skill to implement visual regression testing
|
||||
```
|
||||
|
||||
### Phase 6: Cross-Browser Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `playwright-skill` - Multi-browser
|
||||
- `webapp-testing` - Browser testing
|
||||
|
||||
#### Actions
|
||||
1. Configure Chromium
|
||||
2. Add Firefox tests
|
||||
3. Add WebKit tests
|
||||
4. Test mobile browsers
|
||||
5. Compare results
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @playwright-skill to run cross-browser tests
|
||||
```
|
||||
|
||||
### Phase 7: CI/CD Integration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `github-actions-templates` - GitHub Actions
|
||||
- `cicd-automation-workflow-automate` - CI/CD
|
||||
|
||||
#### Actions
|
||||
1. Create CI workflow
|
||||
2. Configure parallel execution
|
||||
3. Set up artifacts
|
||||
4. Add reporting
|
||||
5. Configure notifications
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @github-actions-templates to integrate E2E tests with CI
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Tests passing
|
||||
- [ ] Coverage adequate
|
||||
- [ ] Visual tests stable
|
||||
- [ ] Cross-browser verified
|
||||
- [ ] CI integration working
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `testing-qa` - Testing workflow
|
||||
- `development` - Development
|
||||
- `web-performance-optimization` - Performance
|
||||
126
skills/godot-4-migration/SKILL.md
Normal file
126
skills/godot-4-migration/SKILL.md
Normal file
@@ -0,0 +1,126 @@
|
||||
---
|
||||
name: godot-4-migration
|
||||
description: Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports.
|
||||
risk: safe
|
||||
source: community
|
||||
---
|
||||
|
||||
# Godot 4 Migration Guide
|
||||
|
||||
## Overview
|
||||
|
||||
A critical guide for developers transitioning from Godot 3.x to Godot 4. This skill focuses on the major syntax changes in GDScript 2.0, the new `Tween` system, and `export` annotation updates.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
- Use when porting a Godot 3 project to Godot 4.
|
||||
- Use when encountering syntax errors after upgrading.
|
||||
- Use when replacing deprecated nodes (like `Tween` node vs `create_tween`).
|
||||
- Use when updating `export` variables to `@export` annotations.
|
||||
|
||||
## Key Changes
|
||||
|
||||
### 1. Annotations (`@`)
|
||||
|
||||
Godot 4 uses `@` for keywords that modify behavior.
|
||||
- `export var x` -> `@export var x`
|
||||
- `onready var y` -> `@onready var y`
|
||||
- `tool` -> `@tool` (at top of file)
|
||||
|
||||
### 2. Setters and Getters
|
||||
|
||||
Properties now define setters/getters inline.
|
||||
|
||||
**Godot 3:**
|
||||
```gdscript
|
||||
var health setget set_health, get_health
|
||||
|
||||
func set_health(value):
|
||||
health = value
|
||||
```
|
||||
|
||||
**Godot 4:**
|
||||
```gdscript
|
||||
var health: int:
|
||||
set(value):
|
||||
health = value
|
||||
emit_signal("health_changed", health)
|
||||
get:
|
||||
return health
|
||||
```
|
||||
|
||||
### 3. Tween System
|
||||
|
||||
The `Tween` node is deprecated. Use `create_tween()` in code.
|
||||
|
||||
**Godot 3:**
|
||||
```gdscript
|
||||
$Tween.interpolate_property(...)
|
||||
$Tween.start()
|
||||
```
|
||||
|
||||
**Godot 4:**
|
||||
```gdscript
|
||||
var tween = create_tween()
|
||||
tween.tween_property($Sprite, "position", Vector2(100, 100), 1.0)
|
||||
tween.parallel().tween_property($Sprite, "modulate:a", 0.0, 1.0)
|
||||
```
|
||||
|
||||
### 4. Signal Connections
|
||||
|
||||
String-based connections are discouraged. Use callables.
|
||||
|
||||
**Godot 3:**
|
||||
```gdscript
|
||||
connect("pressed", self, "_on_pressed")
|
||||
```
|
||||
|
||||
**Godot 4:**
|
||||
```gdscript
|
||||
pressed.connect(_on_pressed)
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Typed Arrays
|
||||
|
||||
GDScript 2.0 supports typed arrays for better performance and type safety.
|
||||
|
||||
```gdscript
|
||||
# Godot 3
|
||||
var enemies = []
|
||||
|
||||
# Godot 4
|
||||
var enemies: Array[Node] = []
|
||||
|
||||
func _ready():
|
||||
for child in get_children():
|
||||
if child is Enemy:
|
||||
enemies.append(child)
|
||||
```
|
||||
|
||||
### Example 2: Awaiting Signals (Coroutines)
|
||||
|
||||
`yield` is replaced by `await`.
|
||||
|
||||
**Godot 3:**
|
||||
```gdscript
|
||||
yield(get_tree().create_timer(1.0), "timeout")
|
||||
```
|
||||
|
||||
**Godot 4:**
|
||||
```gdscript
|
||||
await get_tree().create_timer(1.0).timeout
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
- ✅ **Do:** Use `@export_range`, `@export_file`, etc., for better inspector UI.
|
||||
- ✅ **Do:** Type all variables (`var x: int`) for performance gains in GDScript 2.0.
|
||||
- ✅ **Do:** Use `super()` to call parent methods instead of `.function_name()`.
|
||||
- ❌ **Don't:** Use string names for signals (`emit_signal("name")`) if you can use the signal object (`name.emit()`).
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
**Problem:** "Identifier 'Tween' is not a valid type."
|
||||
**Solution:** `Tween` is now `SceneTreeTween` or just an object returned by `create_tween()`. You rarely type it explicitly, just use `var tween = create_tween()`.
|
||||
100
skills/kotlin-coroutines-expert/SKILL.md
Normal file
100
skills/kotlin-coroutines-expert/SKILL.md
Normal file
@@ -0,0 +1,100 @@
|
||||
---
|
||||
name: kotlin-coroutines-expert
|
||||
description: Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing.
|
||||
risk: safe
|
||||
source: community
|
||||
---
|
||||
|
||||
# Kotlin Coroutines Expert
|
||||
|
||||
## Overview
|
||||
|
||||
A guide to mastering asynchronous programming with Kotlin Coroutines. Covers advanced topics like structured concurrency, `Flow` transformations, exception handling, and testing strategies.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
- Use when implementing asynchronous operations in Kotlin.
|
||||
- Use when designing reactive data streams with `Flow`.
|
||||
- Use when debugging coroutine cancellations or exceptions.
|
||||
- Use when writing unit tests for suspending functions or Flows.
|
||||
|
||||
## Step-by-Step Guide
|
||||
|
||||
### 1. Structured Concurrency
|
||||
|
||||
Always launch coroutines within a defined `CoroutineScope`. Use `coroutineScope` or `supervisorScope` to group concurrent tasks.
|
||||
|
||||
```kotlin
|
||||
suspend fun loadDashboardData(): DashboardData = coroutineScope {
|
||||
val userDeferred = async { userRepo.getUser() }
|
||||
val settingsDeferred = async { settingsRepo.getSettings() }
|
||||
|
||||
DashboardData(
|
||||
user = userDeferred.await(),
|
||||
settings = settingsDeferred.await()
|
||||
)
|
||||
}
|
||||
```
|
||||
|
||||
### 2. Exception Handling
|
||||
|
||||
Use `CoroutineExceptionHandler` for top-level scopes, but rely on `try-catch` within suspending functions for granular control.
|
||||
|
||||
```kotlin
|
||||
val handler = CoroutineExceptionHandler { _, exception ->
|
||||
println("Caught $exception")
|
||||
}
|
||||
|
||||
viewModelScope.launch(handler) {
|
||||
try {
|
||||
riskyOperation()
|
||||
} catch (e: IOException) {
|
||||
// Handle network error specifically
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### 3. Reactive Streams with Flow
|
||||
|
||||
Use `StateFlow` for state that needs to be retained, and `SharedFlow` for events.
|
||||
|
||||
```kotlin
|
||||
// Cold Flow (Lazy)
|
||||
val searchResults: Flow<List<Item>> = searchQuery
|
||||
.debounce(300)
|
||||
.flatMapLatest { query -> searchRepo.search(query) }
|
||||
.flowOn(Dispatchers.IO)
|
||||
|
||||
// Hot Flow (State)
|
||||
val uiState: StateFlow<UiState> = _uiState.asStateFlow()
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Parallel Execution with Error Handling
|
||||
|
||||
```kotlin
|
||||
suspend fun fetchDataWithErrorHandling() = supervisorScope {
|
||||
val task1 = async {
|
||||
try { api.fetchA() } catch (e: Exception) { null }
|
||||
}
|
||||
val task2 = async { api.fetchB() }
|
||||
|
||||
// If task2 fails, task1 is NOT cancelled because of supervisorScope
|
||||
val result1 = task1.await()
|
||||
val result2 = task2.await() // May throw
|
||||
}
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
- ✅ **Do:** Use `Dispatchers.IO` for blocking I/O operations.
|
||||
- ✅ **Do:** Cancel scopes when they are no longer needed (e.g., `ViewModel.onCleared`).
|
||||
- ✅ **Do:** Use `TestScope` and `runTest` for unit testing coroutines.
|
||||
- ❌ **Don't:** Use `GlobalScope`. It breaks structured concurrency and can lead to leaks.
|
||||
- ❌ **Don't:** Catch `CancellationException` unless you rethrow it.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
**Problem:** Coroutine test hangs or fails unpredictably.
|
||||
**Solution:** Ensure you are using `runTest` and injecting `TestDispatcher` into your classes so you can control virtual time.
|
||||
167
skills/kubernetes-deployment/SKILL.md
Normal file
167
skills/kubernetes-deployment/SKILL.md
Normal file
@@ -0,0 +1,167 @@
|
||||
---
|
||||
name: kubernetes-deployment
|
||||
description: "Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: cloud-devops
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Kubernetes Deployment Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for deploying applications to Kubernetes including container orchestration, Helm charts, service mesh configuration, and production-ready K8s patterns.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Deploying to Kubernetes
|
||||
- Creating Helm charts
|
||||
- Configuring service mesh
|
||||
- Setting up K8s networking
|
||||
- Implementing K8s security
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Container Preparation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `docker-expert` - Docker containerization
|
||||
- `k8s-manifest-generator` - K8s manifests
|
||||
|
||||
#### Actions
|
||||
1. Create Dockerfile
|
||||
2. Build container image
|
||||
3. Optimize image size
|
||||
4. Push to registry
|
||||
5. Test container
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @docker-expert to containerize application for K8s
|
||||
```
|
||||
|
||||
### Phase 2: K8s Manifests
|
||||
|
||||
#### Skills to Invoke
|
||||
- `k8s-manifest-generator` - Manifest generation
|
||||
- `kubernetes-architect` - K8s architecture
|
||||
|
||||
#### Actions
|
||||
1. Create Deployment
|
||||
2. Configure Service
|
||||
3. Set up ConfigMap
|
||||
4. Create Secrets
|
||||
5. Add Ingress
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @k8s-manifest-generator to create K8s manifests
|
||||
```
|
||||
|
||||
### Phase 3: Helm Chart
|
||||
|
||||
#### Skills to Invoke
|
||||
- `helm-chart-scaffolding` - Helm charts
|
||||
|
||||
#### Actions
|
||||
1. Create chart structure
|
||||
2. Define values.yaml
|
||||
3. Add templates
|
||||
4. Configure dependencies
|
||||
5. Test chart
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @helm-chart-scaffolding to create Helm chart
|
||||
```
|
||||
|
||||
### Phase 4: Service Mesh
|
||||
|
||||
#### Skills to Invoke
|
||||
- `istio-traffic-management` - Istio
|
||||
- `linkerd-patterns` - Linkerd
|
||||
- `service-mesh-expert` - Service mesh
|
||||
|
||||
#### Actions
|
||||
1. Choose service mesh
|
||||
2. Install mesh
|
||||
3. Configure traffic management
|
||||
4. Set up mTLS
|
||||
5. Add observability
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @istio-traffic-management to configure Istio
|
||||
```
|
||||
|
||||
### Phase 5: Security
|
||||
|
||||
#### Skills to Invoke
|
||||
- `k8s-security-policies` - K8s security
|
||||
- `mtls-configuration` - mTLS
|
||||
|
||||
#### Actions
|
||||
1. Configure RBAC
|
||||
2. Set up NetworkPolicy
|
||||
3. Enable PodSecurity
|
||||
4. Configure secrets
|
||||
5. Implement mTLS
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @k8s-security-policies to secure Kubernetes cluster
|
||||
```
|
||||
|
||||
### Phase 6: Observability
|
||||
|
||||
#### Skills to Invoke
|
||||
- `grafana-dashboards` - Grafana
|
||||
- `prometheus-configuration` - Prometheus
|
||||
|
||||
#### Actions
|
||||
1. Install monitoring stack
|
||||
2. Configure Prometheus
|
||||
3. Create Grafana dashboards
|
||||
4. Set up alerts
|
||||
5. Add distributed tracing
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @prometheus-configuration to set up K8s monitoring
|
||||
```
|
||||
|
||||
### Phase 7: Deployment
|
||||
|
||||
#### Skills to Invoke
|
||||
- `deployment-engineer` - Deployment
|
||||
- `gitops-workflow` - GitOps
|
||||
|
||||
#### Actions
|
||||
1. Configure CI/CD
|
||||
2. Set up GitOps
|
||||
3. Deploy to cluster
|
||||
4. Verify deployment
|
||||
5. Monitor rollout
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @gitops-workflow to implement GitOps deployment
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Containers working
|
||||
- [ ] Manifests valid
|
||||
- [ ] Helm chart installs
|
||||
- [ ] Security configured
|
||||
- [ ] Monitoring active
|
||||
- [ ] Deployment successful
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `cloud-devops` - Cloud/DevOps
|
||||
- `terraform-infrastructure` - Infrastructure
|
||||
- `docker-containerization` - Containers
|
||||
188
skills/libreoffice/base/SKILL.md
Normal file
188
skills/libreoffice/base/SKILL.md
Normal file
@@ -0,0 +1,188 @@
|
||||
---
|
||||
name: base
|
||||
description: "Database management, forms, reports, and data operations with LibreOffice Base."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: office-productivity
|
||||
category: database-processing
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# LibreOffice Base
|
||||
|
||||
## Overview
|
||||
|
||||
LibreOffice Base skill for creating, managing, and automating database workflows using the native ODB (OpenDocument Database) format.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use this skill when:
|
||||
- Creating new databases in ODB format
|
||||
- Connecting to external databases (MySQL, PostgreSQL, etc.)
|
||||
- Automating database operations and reports
|
||||
- Creating forms and reports
|
||||
- Building database applications
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
### 1. Database Creation
|
||||
- Create new ODB databases from scratch
|
||||
- Design tables, views, and relationships
|
||||
- Create embedded HSQLDB/Firebird databases
|
||||
- Connect to external databases
|
||||
|
||||
### 2. Data Operations
|
||||
- Import data from CSV, spreadsheets
|
||||
- Export data to various formats
|
||||
- Query execution and management
|
||||
- Batch data processing
|
||||
|
||||
### 3. Form and Report Automation
|
||||
- Create data entry forms
|
||||
- Design custom reports
|
||||
- Automate report generation
|
||||
- Build form templates
|
||||
|
||||
### 4. Query and SQL
|
||||
- Visual query design
|
||||
- SQL query execution
|
||||
- Query optimization
|
||||
- Result set manipulation
|
||||
|
||||
### 5. Integration
|
||||
- Command-line automation
|
||||
- Python scripting with UNO
|
||||
- JDBC/ODBC connectivity
|
||||
|
||||
## Workflows
|
||||
|
||||
### Creating a New Database
|
||||
|
||||
#### Method 1: Command-Line
|
||||
```bash
|
||||
soffice --base
|
||||
```
|
||||
|
||||
#### Method 2: Python with UNO
|
||||
```python
|
||||
import uno
|
||||
|
||||
def create_database():
|
||||
local_ctx = uno.getComponentContext()
|
||||
resolver = local_ctx.ServiceManager.createInstanceWithContext(
|
||||
"com.sun.star.bridge.UnoUrlResolver", local_ctx
|
||||
)
|
||||
ctx = resolver.resolve(
|
||||
"uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
|
||||
)
|
||||
smgr = ctx.ServiceManager
|
||||
doc = smgr.createInstanceWithContext("com.sun.star.sdb.DatabaseDocument", ctx)
|
||||
doc.storeToURL("file:///path/to/database.odb", ())
|
||||
doc.close(True)
|
||||
```
|
||||
|
||||
### Connecting to External Database
|
||||
|
||||
```python
|
||||
import uno
|
||||
|
||||
def connect_to_mysql(host, port, database, user, password):
|
||||
local_ctx = uno.getComponentContext()
|
||||
resolver = local_ctx.ServiceManager.createInstanceWithContext(
|
||||
"com.sun.star.bridge.UnoUrlResolver", local_ctx
|
||||
)
|
||||
ctx = resolver.resolve(
|
||||
"uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
|
||||
)
|
||||
smgr = ctx.ServiceManager
|
||||
|
||||
doc = smgr.createInstanceWithContext("com.sun.star.sdb.DatabaseDocument", ctx)
|
||||
datasource = doc.getDataSource()
|
||||
datasource.URL = f"sdbc:mysql:jdbc:mysql://{host}:{port}/{database}"
|
||||
datasource.Properties["UserName"] = user
|
||||
datasource.Properties["Password"] = password
|
||||
|
||||
doc.storeToURL("file:///path/to/connected.odb", ())
|
||||
return doc
|
||||
```
|
||||
|
||||
## Database Connection Reference
|
||||
|
||||
### Supported Database Types
|
||||
- HSQLDB (embedded)
|
||||
- Firebird (embedded)
|
||||
- MySQL/MariaDB
|
||||
- PostgreSQL
|
||||
- SQLite
|
||||
- ODBC data sources
|
||||
- JDBC data sources
|
||||
|
||||
### Connection Strings
|
||||
|
||||
```
|
||||
# MySQL
|
||||
sdbc:mysql:jdbc:mysql://localhost:3306/database
|
||||
|
||||
# PostgreSQL
|
||||
sdbc:postgresql://localhost:5432/database
|
||||
|
||||
# SQLite
|
||||
sdbc:sqlite:file:///path/to/database.db
|
||||
|
||||
# ODBC
|
||||
sdbc:odbc:DSN_NAME
|
||||
```
|
||||
|
||||
## Command-Line Reference
|
||||
|
||||
```bash
|
||||
soffice --headless
|
||||
soffice --base # Base
|
||||
```
|
||||
|
||||
## Python Libraries
|
||||
|
||||
```bash
|
||||
pip install pyodbc # ODBC connectivity
|
||||
pip install sqlalchemy # SQL toolkit
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. Use parameterized queries
|
||||
2. Create indexes for performance
|
||||
3. Backup databases regularly
|
||||
4. Use transactions for data integrity
|
||||
5. Store ODB source files in version control
|
||||
6. Document database schema
|
||||
7. Use appropriate data types
|
||||
8. Handle connection errors gracefully
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Cannot open socket
|
||||
```bash
|
||||
killall soffice.bin
|
||||
soffice --headless --accept="socket,host=localhost,port=8100;urp;"
|
||||
```
|
||||
|
||||
### Connection Issues
|
||||
- Verify database server is running
|
||||
- Check connection string format
|
||||
- Ensure JDBC/ODBC drivers are installed
|
||||
- Verify network connectivity
|
||||
|
||||
## Resources
|
||||
|
||||
- [LibreOffice Base Guide](https://documentation.libreoffice.org/)
|
||||
- [UNO API Reference](https://api.libreoffice.org/)
|
||||
- [HSQLDB Documentation](http://hsqldb.org/)
|
||||
- [Firebird Documentation](https://firebirdsql.org/)
|
||||
|
||||
## Related Skills
|
||||
|
||||
- writer
|
||||
- calc
|
||||
- impress
|
||||
- draw
|
||||
- workflow-automation
|
||||
201
skills/libreoffice/calc/SKILL.md
Normal file
201
skills/libreoffice/calc/SKILL.md
Normal file
@@ -0,0 +1,201 @@
|
||||
---
|
||||
name: calc
|
||||
description: "Spreadsheet creation, format conversion (ODS/XLSX/CSV), formulas, data automation with LibreOffice Calc."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: office-productivity
|
||||
category: spreadsheet-processing
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# LibreOffice Calc
|
||||
|
||||
## Overview
|
||||
|
||||
LibreOffice Calc skill for creating, editing, converting, and automating spreadsheet workflows using the native ODS (OpenDocument Spreadsheet) format.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use this skill when:
|
||||
- Creating new spreadsheets in ODS format
|
||||
- Converting between ODS, XLSX, CSV, PDF formats
|
||||
- Automating data processing and analysis
|
||||
- Creating formulas, charts, and pivot tables
|
||||
- Batch processing spreadsheet operations
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
### 1. Spreadsheet Creation
|
||||
- Create new ODS spreadsheets from scratch
|
||||
- Generate spreadsheets from templates
|
||||
- Create data entry forms
|
||||
- Build dashboards and reports
|
||||
|
||||
### 2. Format Conversion
|
||||
- ODS to other formats: XLSX, CSV, PDF, HTML
|
||||
- Other formats to ODS: XLSX, XLS, CSV, DBF
|
||||
- Batch conversion of multiple files
|
||||
|
||||
### 3. Data Automation
|
||||
- Formula automation and calculations
|
||||
- Data import from CSV, database, APIs
|
||||
- Data export to various formats
|
||||
- Batch data processing
|
||||
|
||||
### 4. Data Analysis
|
||||
- Pivot tables and data summarization
|
||||
- Statistical functions and analysis
|
||||
- Data validation and filtering
|
||||
- Conditional formatting
|
||||
|
||||
### 5. Integration
|
||||
- Command-line automation via soffice
|
||||
- Python scripting with UNO
|
||||
- Database connectivity
|
||||
|
||||
## Workflows
|
||||
|
||||
### Creating a New Spreadsheet
|
||||
|
||||
#### Method 1: Command-Line
|
||||
```bash
|
||||
soffice --calc template.ods
|
||||
```
|
||||
|
||||
#### Method 2: Python with UNO
|
||||
```python
|
||||
import uno
|
||||
|
||||
def create_spreadsheet():
|
||||
local_ctx = uno.getComponentContext()
|
||||
resolver = local_ctx.ServiceManager.createInstanceWithContext(
|
||||
"com.sun.star.bridge.UnoUrlResolver", local_ctx
|
||||
)
|
||||
ctx = resolver.resolve(
|
||||
"uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
|
||||
)
|
||||
smgr = ctx.ServiceManager
|
||||
doc = smgr.createInstanceWithContext("com.sun.star.sheet.SpreadsheetDocument", ctx)
|
||||
sheets = doc.getSheets()
|
||||
sheet = sheets.getByIndex(0)
|
||||
cell = sheet.getCellByPosition(0, 0)
|
||||
cell.setString("Hello from LibreOffice Calc!")
|
||||
doc.storeToURL("file:///path/to/spreadsheet.ods", ())
|
||||
doc.close(True)
|
||||
```
|
||||
|
||||
#### Method 3: Using ezodf
|
||||
```python
|
||||
import ezodf
|
||||
|
||||
doc = ezodf.newdoc('ods', 'spreadsheet.ods')
|
||||
sheet = doc.sheets[0]
|
||||
sheet['A1'].set_value('Hello')
|
||||
sheet['B1'].set_value('World')
|
||||
doc.save()
|
||||
```
|
||||
|
||||
### Converting Spreadsheets
|
||||
|
||||
```bash
|
||||
# ODS to XLSX
|
||||
soffice --headless --convert-to xlsx spreadsheet.ods
|
||||
|
||||
# ODS to CSV
|
||||
soffice --headless --convert-to csv spreadsheet.ods
|
||||
|
||||
# ODS to PDF
|
||||
soffice --headless --convert-to pdf spreadsheet.ods
|
||||
|
||||
# XLSX to ODS
|
||||
soffice --headless --convert-to ods spreadsheet.xlsx
|
||||
|
||||
# Batch convert
|
||||
for file in *.ods; do
|
||||
soffice --headless --convert-to xlsx "$file"
|
||||
done
|
||||
```
|
||||
|
||||
### Formula Automation
|
||||
```python
|
||||
import uno
|
||||
|
||||
def create_formula_spreadsheet():
|
||||
local_ctx = uno.getComponentContext()
|
||||
resolver = local_ctx.ServiceManager.createInstanceWithContext(
|
||||
"com.sun.star.bridge.UnoUrlResolver", local_ctx
|
||||
)
|
||||
ctx = resolver.resolve(
|
||||
"uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
|
||||
)
|
||||
smgr = ctx.ServiceManager
|
||||
doc = smgr.createInstanceWithContext("com.sun.star.sheet.SpreadsheetDocument", ctx)
|
||||
sheet = doc.getSheets().getByIndex(0)
|
||||
|
||||
sheet.getCellByPosition(0, 0).setDoubleValue(100)
|
||||
sheet.getCellByPosition(0, 1).setDoubleValue(200)
|
||||
|
||||
cell = sheet.getCellByPosition(0, 2)
|
||||
cell.setFormula("SUM(A1:A2)")
|
||||
|
||||
doc.storeToURL("file:///path/to/formulas.ods", ())
|
||||
doc.close(True)
|
||||
```
|
||||
|
||||
## Format Conversion Reference
|
||||
|
||||
### Supported Input Formats
|
||||
- ODS (native), XLSX, XLS, CSV, DBF, HTML
|
||||
|
||||
### Supported Output Formats
|
||||
- ODS, XLSX, XLS, CSV, PDF, HTML
|
||||
|
||||
## Command-Line Reference
|
||||
|
||||
```bash
|
||||
soffice --headless
|
||||
soffice --headless --convert-to <format> <file>
|
||||
soffice --calc # Calc
|
||||
```
|
||||
|
||||
## Python Libraries
|
||||
|
||||
```bash
|
||||
pip install ezodf # ODS handling
|
||||
pip install odfpy # ODF manipulation
|
||||
pip install pandas # Data analysis
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. Use named ranges for clarity
|
||||
2. Document complex formulas
|
||||
3. Use data validation for input control
|
||||
4. Create templates for recurring reports
|
||||
5. Store ODS source files in version control
|
||||
6. Test conversions thoroughly
|
||||
7. Use CSV for data exchange
|
||||
8. Handle conversion failures gracefully
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Cannot open socket
|
||||
```bash
|
||||
killall soffice.bin
|
||||
soffice --headless --accept="socket,host=localhost,port=8100;urp;"
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
- [LibreOffice Calc Guide](https://documentation.libreoffice.org/)
|
||||
- [UNO API Reference](https://api.libreoffice.org/)
|
||||
- [ezodf Documentation](http://ezodf.rst2.org/)
|
||||
|
||||
## Related Skills
|
||||
|
||||
- writer
|
||||
- impress
|
||||
- draw
|
||||
- base
|
||||
- xlsx-official
|
||||
- workflow-automation
|
||||
165
skills/libreoffice/draw/SKILL.md
Normal file
165
skills/libreoffice/draw/SKILL.md
Normal file
@@ -0,0 +1,165 @@
|
||||
---
|
||||
name: draw
|
||||
description: "Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: office-productivity
|
||||
category: graphics-processing
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# LibreOffice Draw
|
||||
|
||||
## Overview
|
||||
|
||||
LibreOffice Draw skill for creating, editing, converting, and automating vector graphics and diagram workflows using the native ODG (OpenDocument Drawing) format.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use this skill when:
|
||||
- Creating vector graphics and diagrams in ODG format
|
||||
- Converting between ODG, SVG, PDF, PNG formats
|
||||
- Automating diagram and flowchart generation
|
||||
- Creating technical drawings and schematics
|
||||
- Batch processing graphics operations
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
### 1. Graphics Creation
|
||||
- Create new ODG drawings from scratch
|
||||
- Generate diagrams from templates
|
||||
- Create flowcharts and org charts
|
||||
- Design technical drawings
|
||||
|
||||
### 2. Format Conversion
|
||||
- ODG to other formats: SVG, PDF, PNG, JPG
|
||||
- Other formats to ODG: SVG, PDF
|
||||
- Batch conversion of multiple files
|
||||
|
||||
### 3. Diagram Automation
|
||||
- Template-based diagram generation
|
||||
- Automated flowchart creation
|
||||
- Dynamic shape generation
|
||||
- Batch diagram production
|
||||
|
||||
### 4. Graphics Manipulation
|
||||
- Shape creation and manipulation
|
||||
- Path and bezier curve editing
|
||||
- Layer management
|
||||
- Text and label insertion
|
||||
|
||||
### 5. Integration
|
||||
- Command-line automation via soffice
|
||||
- Python scripting with UNO
|
||||
- Integration with workflow tools
|
||||
|
||||
## Workflows
|
||||
|
||||
### Creating a New Drawing
|
||||
|
||||
#### Method 1: Command-Line
|
||||
```bash
|
||||
soffice --draw template.odg
|
||||
```
|
||||
|
||||
#### Method 2: Python with UNO
|
||||
```python
|
||||
import uno
|
||||
|
||||
def create_drawing():
|
||||
local_ctx = uno.getComponentContext()
|
||||
resolver = local_ctx.ServiceManager.createInstanceWithContext(
|
||||
"com.sun.star.bridge.UnoUrlResolver", local_ctx
|
||||
)
|
||||
ctx = resolver.resolve(
|
||||
"uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
|
||||
)
|
||||
smgr = ctx.ServiceManager
|
||||
doc = smgr.createInstanceWithContext("com.sun.star.drawing.DrawingDocument", ctx)
|
||||
page = doc.getDrawPages().getByIndex(0)
|
||||
doc.storeToURL("file:///path/to/drawing.odg", ())
|
||||
doc.close(True)
|
||||
```
|
||||
|
||||
### Converting Drawings
|
||||
|
||||
```bash
|
||||
# ODG to SVG
|
||||
soffice --headless --convert-to svg drawing.odg
|
||||
|
||||
# ODG to PDF
|
||||
soffice --headless --convert-to pdf drawing.odg
|
||||
|
||||
# ODG to PNG
|
||||
soffice --headless --convert-to png:PNG_drawing drawing.odg
|
||||
|
||||
# SVG to ODG
|
||||
soffice --headless --convert-to odg drawing.svg
|
||||
|
||||
# Batch convert
|
||||
for file in *.odg; do
|
||||
soffice --headless --convert-to pdf "$file"
|
||||
done
|
||||
```
|
||||
|
||||
## Format Conversion Reference
|
||||
|
||||
### Supported Input Formats
|
||||
- ODG (native), SVG, PDF
|
||||
|
||||
### Supported Output Formats
|
||||
- ODG, SVG, PDF, PNG, JPG, GIF, BMP, WMF, EMF
|
||||
|
||||
## Command-Line Reference
|
||||
|
||||
```bash
|
||||
soffice --headless
|
||||
soffice --headless --convert-to <format> <file>
|
||||
soffice --draw # Draw
|
||||
```
|
||||
|
||||
## Python Libraries
|
||||
|
||||
```bash
|
||||
pip install ezodf # ODF handling
|
||||
pip install odfpy # ODF manipulation
|
||||
pip install svgwrite # SVG generation
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. Use layers for organization
|
||||
2. Create templates for recurring diagrams
|
||||
3. Use vector formats for scalability
|
||||
4. Name objects for easy reference
|
||||
5. Store ODG source files in version control
|
||||
6. Test conversions thoroughly
|
||||
7. Export to SVG for web use
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Cannot open socket
|
||||
```bash
|
||||
killall soffice.bin
|
||||
soffice --headless --accept="socket,host=localhost,port=8100;urp;"
|
||||
```
|
||||
|
||||
### Quality Issues in PNG Export
|
||||
```bash
|
||||
soffice --headless --convert-to png:PNG_drawing_Export \
|
||||
--filterData='{"Width":2048,"Height":2048}' drawing.odg
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
- [LibreOffice Draw Guide](https://documentation.libreoffice.org/)
|
||||
- [UNO API Reference](https://api.libreoffice.org/)
|
||||
- [SVG Specification](https://www.w3.org/TR/SVG/)
|
||||
|
||||
## Related Skills
|
||||
|
||||
- writer
|
||||
- calc
|
||||
- impress
|
||||
- base
|
||||
- workflow-automation
|
||||
174
skills/libreoffice/impress/SKILL.md
Normal file
174
skills/libreoffice/impress/SKILL.md
Normal file
@@ -0,0 +1,174 @@
|
||||
---
|
||||
name: impress
|
||||
description: "Presentation creation, format conversion (ODP/PPTX/PDF), slide automation with LibreOffice Impress."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: office-productivity
|
||||
category: presentation-processing
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# LibreOffice Impress
|
||||
|
||||
## Overview
|
||||
|
||||
LibreOffice Impress skill for creating, editing, converting, and automating presentation workflows using the native ODP (OpenDocument Presentation) format.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use this skill when:
|
||||
- Creating new presentations in ODP format
|
||||
- Converting between ODP, PPTX, PDF formats
|
||||
- Automating slide generation from templates
|
||||
- Batch processing presentation operations
|
||||
- Creating presentation templates
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
### 1. Presentation Creation
|
||||
- Create new ODP presentations from scratch
|
||||
- Generate presentations from templates
|
||||
- Create slide masters and layouts
|
||||
- Build interactive presentations
|
||||
|
||||
### 2. Format Conversion
|
||||
- ODP to other formats: PPTX, PDF, HTML, SWF
|
||||
- Other formats to ODP: PPTX, PPT, PDF
|
||||
- Batch conversion of multiple files
|
||||
|
||||
### 3. Slide Automation
|
||||
- Template-based slide generation
|
||||
- Batch slide creation from data
|
||||
- Automated content insertion
|
||||
- Dynamic chart generation
|
||||
|
||||
### 4. Content Manipulation
|
||||
- Text and image insertion
|
||||
- Shape and diagram creation
|
||||
- Animation and transition control
|
||||
- Speaker notes management
|
||||
|
||||
### 5. Integration
|
||||
- Command-line automation via soffice
|
||||
- Python scripting with UNO
|
||||
- Integration with workflow tools
|
||||
|
||||
## Workflows
|
||||
|
||||
### Creating a New Presentation
|
||||
|
||||
#### Method 1: Command-Line
|
||||
```bash
|
||||
soffice --impress template.odp
|
||||
```
|
||||
|
||||
#### Method 2: Python with UNO
|
||||
```python
|
||||
import uno
|
||||
|
||||
def create_presentation():
|
||||
local_ctx = uno.getComponentContext()
|
||||
resolver = local_ctx.ServiceManager.createInstanceWithContext(
|
||||
"com.sun.star.bridge.UnoUrlResolver", local_ctx
|
||||
)
|
||||
ctx = resolver.resolve(
|
||||
"uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
|
||||
)
|
||||
smgr = ctx.ServiceManager
|
||||
doc = smgr.createInstanceWithContext("com.sun.star.presentation.PresentationDocument", ctx)
|
||||
slides = doc.getDrawPages()
|
||||
slide = slides.getByIndex(0)
|
||||
doc.storeToURL("file:///path/to/presentation.odp", ())
|
||||
doc.close(True)
|
||||
```
|
||||
|
||||
### Converting Presentations
|
||||
|
||||
```bash
|
||||
# ODP to PPTX
|
||||
soffice --headless --convert-to pptx presentation.odp
|
||||
|
||||
# ODP to PDF
|
||||
soffice --headless --convert-to pdf presentation.odp
|
||||
|
||||
# PPTX to ODP
|
||||
soffice --headless --convert-to odp presentation.pptx
|
||||
|
||||
# Batch convert
|
||||
for file in *.odp; do
|
||||
soffice --headless --convert-to pdf "$file"
|
||||
done
|
||||
```
|
||||
|
||||
### Template-Based Generation
|
||||
```python
|
||||
import subprocess
|
||||
import tempfile
|
||||
from pathlib import Path
|
||||
|
||||
def generate_from_template(template_path, content, output_path):
|
||||
with tempfile.TemporaryDirectory() as tmpdir:
|
||||
subprocess.run(['unzip', '-q', template_path, '-d', tmpdir])
|
||||
content_file = Path(tmpdir) / 'content.xml'
|
||||
content_xml = content_file.read_text()
|
||||
for key, value in content.items():
|
||||
content_xml = content_xml.replace(f'${{{key}}}', str(value))
|
||||
content_file.write_text(content_xml)
|
||||
subprocess.run(['zip', '-rq', output_path, '.'], cwd=tmpdir)
|
||||
return output_path
|
||||
```
|
||||
|
||||
## Format Conversion Reference
|
||||
|
||||
### Supported Input Formats
|
||||
- ODP (native), PPTX, PPT, PDF
|
||||
|
||||
### Supported Output Formats
|
||||
- ODP, PPTX, PDF, HTML, SWF
|
||||
|
||||
## Command-Line Reference
|
||||
|
||||
```bash
|
||||
soffice --headless
|
||||
soffice --headless --convert-to <format> <file>
|
||||
soffice --impress # Impress
|
||||
```
|
||||
|
||||
## Python Libraries
|
||||
|
||||
```bash
|
||||
pip install ezodf # ODF handling
|
||||
pip install odfpy # ODF manipulation
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. Use slide masters for consistency
|
||||
2. Create templates for recurring presentations
|
||||
3. Embed fonts for PDF distribution
|
||||
4. Use vector graphics when possible
|
||||
5. Store ODP source files in version control
|
||||
6. Test conversions thoroughly
|
||||
7. Keep file sizes manageable
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Cannot open socket
|
||||
```bash
|
||||
killall soffice.bin
|
||||
soffice --headless --accept="socket,host=localhost,port=8100;urp;"
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
- [LibreOffice Impress Guide](https://documentation.libreoffice.org/)
|
||||
- [UNO API Reference](https://api.libreoffice.org/)
|
||||
|
||||
## Related Skills
|
||||
|
||||
- writer
|
||||
- calc
|
||||
- draw
|
||||
- base
|
||||
- pptx-official
|
||||
- workflow-automation
|
||||
200
skills/libreoffice/writer/SKILL.md
Normal file
200
skills/libreoffice/writer/SKILL.md
Normal file
@@ -0,0 +1,200 @@
|
||||
---
|
||||
name: writer
|
||||
description: "Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: office-productivity
|
||||
category: document-processing
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# LibreOffice Writer
|
||||
|
||||
## Overview
|
||||
|
||||
LibreOffice Writer skill for creating, editing, converting, and automating document workflows using the native ODT (OpenDocument Text) format.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use this skill when:
|
||||
- Creating new documents in ODT format
|
||||
- Converting documents between formats (ODT <-> DOCX, PDF, HTML, RTF, TXT)
|
||||
- Automating document generation workflows
|
||||
- Performing batch document operations
|
||||
- Creating templates and standardized document formats
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
### 1. Document Creation
|
||||
- Create new ODT documents from scratch
|
||||
- Generate documents from templates
|
||||
- Create mail merge documents
|
||||
- Build forms with fillable fields
|
||||
|
||||
### 2. Format Conversion
|
||||
- ODT to other formats: DOCX, PDF, HTML, RTF, TXT, EPUB
|
||||
- Other formats to ODT: DOCX, DOC, RTF, HTML, TXT
|
||||
- Batch conversion of multiple documents
|
||||
|
||||
### 3. Document Automation
|
||||
- Template-based document generation
|
||||
- Mail merge with data sources (CSV, spreadsheet, database)
|
||||
- Batch document processing
|
||||
- Automated report generation
|
||||
|
||||
### 4. Content Manipulation
|
||||
- Text extraction and insertion
|
||||
- Style management and application
|
||||
- Table creation and manipulation
|
||||
- Header/footer management
|
||||
|
||||
### 5. Integration
|
||||
- Command-line automation via soffice
|
||||
- Python scripting with UNO
|
||||
- Integration with workflow automation tools
|
||||
|
||||
## Workflows
|
||||
|
||||
### Creating a New Document
|
||||
|
||||
#### Method 1: Command-Line
|
||||
```bash
|
||||
soffice --writer template.odt
|
||||
```
|
||||
|
||||
#### Method 2: Python with UNO
|
||||
```python
|
||||
import uno
|
||||
|
||||
def create_document():
|
||||
local_ctx = uno.getComponentContext()
|
||||
resolver = local_ctx.ServiceManager.createInstanceWithContext(
|
||||
"com.sun.star.bridge.UnoUrlResolver", local_ctx
|
||||
)
|
||||
ctx = resolver.resolve(
|
||||
"uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
|
||||
)
|
||||
smgr = ctx.ServiceManager
|
||||
doc = smgr.createInstanceWithContext("com.sun.star.text.TextDocument", ctx)
|
||||
text = doc.Text
|
||||
cursor = text.createTextCursor()
|
||||
text.insertString(cursor, "Hello from LibreOffice Writer!", 0)
|
||||
doc.storeToURL("file:///path/to/document.odt", ())
|
||||
doc.close(True)
|
||||
```
|
||||
|
||||
#### Method 3: Using odfpy
|
||||
```python
|
||||
from odf.opendocument import OpenDocumentText
|
||||
from odf.text import P, H
|
||||
|
||||
doc = OpenDocumentText()
|
||||
h1 = H(outlinelevel='1', text='Document Title')
|
||||
doc.text.appendChild(h1)
|
||||
doc.save("document.odt")
|
||||
```
|
||||
|
||||
### Converting Documents
|
||||
|
||||
```bash
|
||||
# ODT to DOCX
|
||||
soffice --headless --convert-to docx document.odt
|
||||
|
||||
# ODT to PDF
|
||||
soffice --headless --convert-to pdf document.odt
|
||||
|
||||
# DOCX to ODT
|
||||
soffice --headless --convert-to odt document.docx
|
||||
|
||||
# Batch convert
|
||||
for file in *.odt; do
|
||||
soffice --headless --convert-to pdf "$file"
|
||||
done
|
||||
```
|
||||
|
||||
### Template-Based Generation
|
||||
```python
|
||||
import subprocess
|
||||
import tempfile
|
||||
from pathlib import Path
|
||||
|
||||
def generate_from_template(template_path, variables, output_path):
|
||||
with tempfile.TemporaryDirectory() as tmpdir:
|
||||
subprocess.run(['unzip', '-q', template_path, '-d', tmpdir])
|
||||
content_file = Path(tmpdir) / 'content.xml'
|
||||
content = content_file.read_text()
|
||||
for key, value in variables.items():
|
||||
content = content.replace(f'${{{key}}}', str(value))
|
||||
content_file.write_text(content)
|
||||
subprocess.run(['zip', '-rq', output_path, '.'], cwd=tmpdir)
|
||||
return output_path
|
||||
```
|
||||
|
||||
## Format Conversion Reference
|
||||
|
||||
### Supported Input Formats
|
||||
- ODT (native), DOCX, DOC, RTF, HTML, TXT, EPUB
|
||||
|
||||
### Supported Output Formats
|
||||
- ODT, DOCX, PDF, PDF/A, HTML, RTF, TXT, EPUB
|
||||
|
||||
## Command-Line Reference
|
||||
|
||||
```bash
|
||||
soffice --headless
|
||||
soffice --headless --convert-to <format> <file>
|
||||
soffice --writer # Writer
|
||||
soffice --calc # Calc
|
||||
soffice --impress # Impress
|
||||
soffice --draw # Draw
|
||||
```
|
||||
|
||||
## Python Libraries
|
||||
|
||||
```bash
|
||||
pip install odfpy # ODF manipulation
|
||||
pip install ezodf # Easier ODF handling
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. Use styles for consistency
|
||||
2. Create templates for recurring documents
|
||||
3. Ensure accessibility (heading hierarchy, alt text)
|
||||
4. Fill document metadata
|
||||
5. Store ODT source files in version control
|
||||
6. Test conversions thoroughly
|
||||
7. Embed fonts for PDF distribution
|
||||
8. Handle conversion failures gracefully
|
||||
9. Log automation operations
|
||||
10. Clean temporary files
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Cannot open socket
|
||||
```bash
|
||||
killall soffice.bin
|
||||
soffice --headless --accept="socket,host=localhost,port=8100;urp;"
|
||||
```
|
||||
|
||||
### Conversion Quality Issues
|
||||
```bash
|
||||
soffice --headless --convert-to pdf:writer_pdf_Export document.odt
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
- [LibreOffice Writer Guide](https://documentation.libreoffice.org/)
|
||||
- [LibreOffice SDK](https://wiki.documentfoundation.org/Documentation/DevGuide)
|
||||
- [UNO API Reference](https://api.libreoffice.org/)
|
||||
- [odfpy](https://pypi.org/project/odfpy/)
|
||||
|
||||
## Related Skills
|
||||
|
||||
- calc
|
||||
- impress
|
||||
- draw
|
||||
- base
|
||||
- docx-official
|
||||
- pdf-official
|
||||
- workflow-automation
|
||||
221
skills/linux-troubleshooting/SKILL.md
Normal file
221
skills/linux-troubleshooting/SKILL.md
Normal file
@@ -0,0 +1,221 @@
|
||||
---
|
||||
name: linux-troubleshooting
|
||||
description: "Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: system-administration
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Linux Troubleshooting Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for diagnosing and resolving Linux system issues including performance problems, service failures, network issues, and resource constraints.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Diagnosing system performance issues
|
||||
- Troubleshooting service failures
|
||||
- Investigating network problems
|
||||
- Resolving disk space issues
|
||||
- Debugging application errors
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Initial Assessment
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-linux` - Linux commands
|
||||
- `devops-troubleshooter` - Troubleshooting
|
||||
|
||||
#### Actions
|
||||
1. Check system uptime
|
||||
2. Review recent changes
|
||||
3. Identify symptoms
|
||||
4. Gather error messages
|
||||
5. Document findings
|
||||
|
||||
#### Commands
|
||||
```bash
|
||||
uptime
|
||||
hostnamectl
|
||||
cat /etc/os-release
|
||||
dmesg | tail -50
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @bash-linux to gather system information
|
||||
```
|
||||
|
||||
### Phase 2: Resource Analysis
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-linux` - Resource commands
|
||||
- `performance-engineer` - Performance analysis
|
||||
|
||||
#### Actions
|
||||
1. Check CPU usage
|
||||
2. Analyze memory
|
||||
3. Review disk space
|
||||
4. Monitor I/O
|
||||
5. Check network
|
||||
|
||||
#### Commands
|
||||
```bash
|
||||
top -bn1 | head -20
|
||||
free -h
|
||||
df -h
|
||||
iostat -x 1 5
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @performance-engineer to analyze system resources
|
||||
```
|
||||
|
||||
### Phase 3: Process Investigation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-linux` - Process commands
|
||||
- `server-management` - Process management
|
||||
|
||||
#### Actions
|
||||
1. List running processes
|
||||
2. Identify resource hogs
|
||||
3. Check process status
|
||||
4. Review process trees
|
||||
5. Analyze strace output
|
||||
|
||||
#### Commands
|
||||
```bash
|
||||
ps aux --sort=-%cpu | head -10
|
||||
pstree -p
|
||||
lsof -p PID
|
||||
strace -p PID
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @server-management to investigate processes
|
||||
```
|
||||
|
||||
### Phase 4: Log Analysis
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-linux` - Log commands
|
||||
- `error-detective` - Error detection
|
||||
|
||||
#### Actions
|
||||
1. Check system logs
|
||||
2. Review application logs
|
||||
3. Search for errors
|
||||
4. Analyze log patterns
|
||||
5. Correlate events
|
||||
|
||||
#### Commands
|
||||
```bash
|
||||
journalctl -xe
|
||||
tail -f /var/log/syslog
|
||||
grep -i error /var/log/*
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @error-detective to analyze log files
|
||||
```
|
||||
|
||||
### Phase 5: Network Diagnostics
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-linux` - Network commands
|
||||
- `network-engineer` - Network troubleshooting
|
||||
|
||||
#### Actions
|
||||
1. Check network interfaces
|
||||
2. Test connectivity
|
||||
3. Analyze connections
|
||||
4. Review firewall rules
|
||||
5. Check DNS resolution
|
||||
|
||||
#### Commands
|
||||
```bash
|
||||
ip addr show
|
||||
ss -tulpn
|
||||
curl -v http://target
|
||||
dig domain
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @network-engineer to diagnose network issues
|
||||
```
|
||||
|
||||
### Phase 6: Service Troubleshooting
|
||||
|
||||
#### Skills to Invoke
|
||||
- `server-management` - Service management
|
||||
- `systematic-debugging` - Debugging
|
||||
|
||||
#### Actions
|
||||
1. Check service status
|
||||
2. Review service logs
|
||||
3. Test service restart
|
||||
4. Verify dependencies
|
||||
5. Check configuration
|
||||
|
||||
#### Commands
|
||||
```bash
|
||||
systemctl status service
|
||||
journalctl -u service -f
|
||||
systemctl restart service
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @systematic-debugging to troubleshoot service issues
|
||||
```
|
||||
|
||||
### Phase 7: Resolution
|
||||
|
||||
#### Skills to Invoke
|
||||
- `incident-responder` - Incident response
|
||||
- `bash-pro` - Fix implementation
|
||||
|
||||
#### Actions
|
||||
1. Implement fix
|
||||
2. Verify resolution
|
||||
3. Monitor stability
|
||||
4. Document solution
|
||||
5. Create prevention plan
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @incident-responder to implement resolution
|
||||
```
|
||||
|
||||
## Troubleshooting Checklist
|
||||
|
||||
- [ ] System information gathered
|
||||
- [ ] Resources analyzed
|
||||
- [ ] Logs reviewed
|
||||
- [ ] Network tested
|
||||
- [ ] Services verified
|
||||
- [ ] Issue resolved
|
||||
- [ ] Documentation created
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Root cause identified
|
||||
- [ ] Fix verified
|
||||
- [ ] Monitoring in place
|
||||
- [ ] Documentation complete
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `os-scripting` - OS scripting
|
||||
- `bash-scripting` - Bash scripting
|
||||
- `cloud-devops` - DevOps
|
||||
219
skills/office-productivity/SKILL.md
Normal file
219
skills/office-productivity/SKILL.md
Normal file
@@ -0,0 +1,219 @@
|
||||
---
|
||||
name: office-productivity
|
||||
description: "Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: office-productivity
|
||||
category: workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Office Productivity Workflow Bundle
|
||||
|
||||
## Overview
|
||||
|
||||
Comprehensive office productivity workflow for document creation, spreadsheet automation, presentation generation, and format conversion using LibreOffice and Microsoft Office tools.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Creating office documents programmatically
|
||||
- Automating document workflows
|
||||
- Converting between document formats
|
||||
- Generating reports
|
||||
- Creating presentations from data
|
||||
- Processing spreadsheets
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Document Creation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `libreoffice-writer` - LibreOffice Writer
|
||||
- `docx-official` - Microsoft Word
|
||||
- `pdf-official` - PDF handling
|
||||
|
||||
#### Actions
|
||||
1. Design document template
|
||||
2. Create document structure
|
||||
3. Add content programmatically
|
||||
4. Apply formatting
|
||||
5. Export to required formats
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @libreoffice-writer to create ODT documents
|
||||
```
|
||||
|
||||
```
|
||||
Use @docx-official to create Word documents
|
||||
```
|
||||
|
||||
### Phase 2: Spreadsheet Automation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `libreoffice-calc` - LibreOffice Calc
|
||||
- `xlsx-official` - Excel spreadsheets
|
||||
- `googlesheets-automation` - Google Sheets
|
||||
|
||||
#### Actions
|
||||
1. Design spreadsheet structure
|
||||
2. Create formulas
|
||||
3. Import data
|
||||
4. Generate charts
|
||||
5. Export reports
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @libreoffice-calc to create ODS spreadsheets
|
||||
```
|
||||
|
||||
```
|
||||
Use @xlsx-official to create Excel reports
|
||||
```
|
||||
|
||||
### Phase 3: Presentation Generation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `libreoffice-impress` - LibreOffice Impress
|
||||
- `pptx-official` - PowerPoint
|
||||
- `frontend-slides` - HTML slides
|
||||
- `nanobanana-ppt-skills` - AI PPT generation
|
||||
|
||||
#### Actions
|
||||
1. Design slide template
|
||||
2. Generate slides from data
|
||||
3. Add charts and graphics
|
||||
4. Apply animations
|
||||
5. Export presentations
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @libreoffice-impress to create ODP presentations
|
||||
```
|
||||
|
||||
```
|
||||
Use @pptx-official to create PowerPoint presentations
|
||||
```
|
||||
|
||||
```
|
||||
Use @frontend-slides to create HTML presentations
|
||||
```
|
||||
|
||||
### Phase 4: Format Conversion
|
||||
|
||||
#### Skills to Invoke
|
||||
- `libreoffice-writer` - Document conversion
|
||||
- `libreoffice-calc` - Spreadsheet conversion
|
||||
- `pdf-official` - PDF conversion
|
||||
|
||||
#### Actions
|
||||
1. Identify source format
|
||||
2. Choose target format
|
||||
3. Perform conversion
|
||||
4. Verify quality
|
||||
5. Batch process files
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @libreoffice-writer to convert documents
|
||||
```
|
||||
|
||||
### Phase 5: Document Automation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `libreoffice-writer` - Mail merge
|
||||
- `workflow-automation` - Workflow automation
|
||||
- `file-organizer` - File organization
|
||||
|
||||
#### Actions
|
||||
1. Design automation workflow
|
||||
2. Create templates
|
||||
3. Set up data sources
|
||||
4. Generate documents
|
||||
5. Distribute outputs
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @libreoffice-writer to perform mail merge
|
||||
```
|
||||
|
||||
```
|
||||
Use @workflow-automation to automate document workflows
|
||||
```
|
||||
|
||||
### Phase 6: Graphics and Diagrams
|
||||
|
||||
#### Skills to Invoke
|
||||
- `libreoffice-draw` - Vector graphics
|
||||
- `canvas-design` - Canvas design
|
||||
- `mermaid-expert` - Diagram generation
|
||||
|
||||
#### Actions
|
||||
1. Design graphics
|
||||
2. Create diagrams
|
||||
3. Generate charts
|
||||
4. Export images
|
||||
5. Integrate with documents
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @libreoffice-draw to create vector graphics
|
||||
```
|
||||
|
||||
```
|
||||
Use @mermaid-expert to create diagrams
|
||||
```
|
||||
|
||||
### Phase 7: Database Integration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `libreoffice-base` - LibreOffice Base
|
||||
- `database-architect` - Database design
|
||||
|
||||
#### Actions
|
||||
1. Connect to data sources
|
||||
2. Create forms
|
||||
3. Design reports
|
||||
4. Automate queries
|
||||
5. Generate output
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @libreoffice-base to create database reports
|
||||
```
|
||||
|
||||
## Office Application Workflows
|
||||
|
||||
### LibreOffice
|
||||
```
|
||||
Skills: libreoffice-writer, libreoffice-calc, libreoffice-impress, libreoffice-draw, libreoffice-base
|
||||
Formats: ODT, ODS, ODP, ODG, ODB
|
||||
```
|
||||
|
||||
### Microsoft Office
|
||||
```
|
||||
Skills: docx-official, xlsx-official, pptx-official
|
||||
Formats: DOCX, XLSX, PPTX
|
||||
```
|
||||
|
||||
### Google Workspace
|
||||
```
|
||||
Skills: googlesheets-automation, google-drive-automation, gmail-automation
|
||||
Formats: Google Docs, Sheets, Slides
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Documents formatted correctly
|
||||
- [ ] Formulas working
|
||||
- [ ] Presentations complete
|
||||
- [ ] Conversions successful
|
||||
- [ ] Automation tested
|
||||
- [ ] Files organized
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - Application development
|
||||
- `documentation` - Documentation generation
|
||||
- `database` - Data integration
|
||||
429
skills/os-scripting/SKILL.md
Normal file
429
skills/os-scripting/SKILL.md
Normal file
@@ -0,0 +1,429 @@
|
||||
---
|
||||
name: os-scripting
|
||||
description: "Operating system and shell scripting troubleshooting workflow for Linux, macOS, and Windows. Covers bash scripting, system administration, debugging, and automation."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: system-administration
|
||||
category: workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# OS/Shell Scripting Troubleshooting Workflow Bundle
|
||||
|
||||
## Overview
|
||||
|
||||
Comprehensive workflow for operating system troubleshooting, shell scripting, and system administration across Linux, macOS, and Windows. This bundle orchestrates skills for debugging system issues, creating robust scripts, and automating administrative tasks.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Debugging shell script errors
|
||||
- Creating production-ready bash scripts
|
||||
- Troubleshooting system issues
|
||||
- Automating system administration tasks
|
||||
- Managing processes and services
|
||||
- Configuring system resources
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Environment Assessment
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-linux` - Linux bash patterns
|
||||
- `bash-pro` - Professional bash scripting
|
||||
- `bash-defensive-patterns` - Defensive scripting
|
||||
|
||||
#### Actions
|
||||
1. Identify operating system and version
|
||||
2. Check available tools and commands
|
||||
3. Verify permissions and access
|
||||
4. Assess system resources
|
||||
5. Review logs and error messages
|
||||
|
||||
#### Diagnostic Commands
|
||||
```bash
|
||||
# System information
|
||||
uname -a
|
||||
cat /etc/os-release
|
||||
hostnamectl
|
||||
|
||||
# Resource usage
|
||||
top
|
||||
htop
|
||||
df -h
|
||||
free -m
|
||||
|
||||
# Process information
|
||||
ps aux
|
||||
pgrep -f pattern
|
||||
lsof -i :port
|
||||
|
||||
# Network status
|
||||
netstat -tulpn
|
||||
ss -tulpn
|
||||
ip addr show
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @bash-linux to diagnose system performance issues
|
||||
```
|
||||
|
||||
### Phase 2: Script Analysis
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-defensive-patterns` - Defensive scripting
|
||||
- `shellcheck-configuration` - ShellCheck linting
|
||||
- `bats-testing-patterns` - Bats testing
|
||||
|
||||
#### Actions
|
||||
1. Run ShellCheck for linting
|
||||
2. Analyze script structure
|
||||
3. Identify potential issues
|
||||
4. Check error handling
|
||||
5. Verify variable usage
|
||||
|
||||
#### ShellCheck Usage
|
||||
```bash
|
||||
# Install ShellCheck
|
||||
sudo apt install shellcheck # Debian/Ubuntu
|
||||
brew install shellcheck # macOS
|
||||
|
||||
# Run ShellCheck
|
||||
shellcheck script.sh
|
||||
shellcheck -f gcc script.sh
|
||||
|
||||
# Fix common issues
|
||||
# - Use quotes around variables
|
||||
# - Check exit codes
|
||||
# - Handle errors properly
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @shellcheck-configuration to lint and fix shell scripts
|
||||
```
|
||||
|
||||
### Phase 3: Debugging
|
||||
|
||||
#### Skills to Invoke
|
||||
- `systematic-debugging` - Systematic debugging
|
||||
- `debugger` - Debugging specialist
|
||||
- `error-detective` - Error pattern detection
|
||||
|
||||
#### Actions
|
||||
1. Enable debug mode
|
||||
2. Add logging statements
|
||||
3. Trace execution flow
|
||||
4. Isolate failing sections
|
||||
5. Test components individually
|
||||
|
||||
#### Debug Techniques
|
||||
```bash
|
||||
# Enable debug mode
|
||||
set -x # Print commands
|
||||
set -e # Exit on error
|
||||
set -u # Exit on undefined variable
|
||||
set -o pipefail # Pipeline failure detection
|
||||
|
||||
# Add logging
|
||||
log() {
|
||||
echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*" >> /var/log/script.log
|
||||
}
|
||||
|
||||
# Trap errors
|
||||
trap 'echo "Error on line $LINENO"' ERR
|
||||
|
||||
# Test sections
|
||||
bash -n script.sh # Syntax check
|
||||
bash -x script.sh # Trace execution
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @systematic-debugging to trace and fix shell script errors
|
||||
```
|
||||
|
||||
### Phase 4: Script Development
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bash-pro` - Professional scripting
|
||||
- `bash-defensive-patterns` - Defensive patterns
|
||||
- `linux-shell-scripting` - Shell scripting
|
||||
|
||||
#### Actions
|
||||
1. Design script structure
|
||||
2. Implement functions
|
||||
3. Add error handling
|
||||
4. Include input validation
|
||||
5. Add help documentation
|
||||
|
||||
#### Script Template
|
||||
```bash
|
||||
#!/usr/bin/env bash
|
||||
set -euo pipefail
|
||||
|
||||
# Constants
|
||||
readonly SCRIPT_NAME=$(basename "$0")
|
||||
readonly SCRIPT_DIR=$(cd "$(dirname "$0")" && pwd)
|
||||
|
||||
# Logging
|
||||
log() {
|
||||
local level="$1"
|
||||
shift
|
||||
echo "[$(date '+%Y-%m-%d %H:%M:%S')] [$level] $*" >&2
|
||||
}
|
||||
|
||||
info() { log "INFO" "$@"; }
|
||||
warn() { log "WARN" "$@"; }
|
||||
error() { log "ERROR" "$@"; exit 1; }
|
||||
|
||||
# Usage
|
||||
usage() {
|
||||
cat <<EOF
|
||||
Usage: $SCRIPT_NAME [OPTIONS]
|
||||
|
||||
Options:
|
||||
-h, --help Show this help message
|
||||
-v, --verbose Enable verbose output
|
||||
-d, --debug Enable debug mode
|
||||
|
||||
Examples:
|
||||
$SCRIPT_NAME --verbose
|
||||
$SCRIPT_NAME -d
|
||||
EOF
|
||||
}
|
||||
|
||||
# Main function
|
||||
main() {
|
||||
local verbose=false
|
||||
local debug=false
|
||||
|
||||
while [[ $# -gt 0 ]]; do
|
||||
case "$1" in
|
||||
-h|--help)
|
||||
usage
|
||||
exit 0
|
||||
;;
|
||||
-v|--verbose)
|
||||
verbose=true
|
||||
shift
|
||||
;;
|
||||
-d|--debug)
|
||||
debug=true
|
||||
set -x
|
||||
shift
|
||||
;;
|
||||
*)
|
||||
error "Unknown option: $1"
|
||||
;;
|
||||
esac
|
||||
done
|
||||
|
||||
info "Script started"
|
||||
# Your code here
|
||||
info "Script completed"
|
||||
}
|
||||
|
||||
main "$@"
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @bash-pro to create a production-ready backup script
|
||||
```
|
||||
|
||||
```
|
||||
Use @linux-shell-scripting to automate system maintenance tasks
|
||||
```
|
||||
|
||||
### Phase 5: Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `bats-testing-patterns` - Bats testing framework
|
||||
- `test-automator` - Test automation
|
||||
|
||||
#### Actions
|
||||
1. Write Bats tests
|
||||
2. Test edge cases
|
||||
3. Test error conditions
|
||||
4. Verify expected outputs
|
||||
5. Run test suite
|
||||
|
||||
#### Bats Test Example
|
||||
```bash
|
||||
#!/usr/bin/env bats
|
||||
|
||||
@test "script returns success" {
|
||||
run ./script.sh
|
||||
[ "$status" -eq 0 ]
|
||||
}
|
||||
|
||||
@test "script handles missing arguments" {
|
||||
run ./script.sh
|
||||
[ "$status" -ne 0 ]
|
||||
[ "$output" == *"Usage:"* ]
|
||||
}
|
||||
|
||||
@test "script creates expected output" {
|
||||
run ./script.sh --output test.txt
|
||||
[ -f "test.txt" ]
|
||||
}
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @bats-testing-patterns to write tests for shell scripts
|
||||
```
|
||||
|
||||
### Phase 6: System Troubleshooting
|
||||
|
||||
#### Skills to Invoke
|
||||
- `devops-troubleshooter` - DevOps troubleshooting
|
||||
- `incident-responder` - Incident response
|
||||
- `server-management` - Server management
|
||||
|
||||
#### Actions
|
||||
1. Identify symptoms
|
||||
2. Check system logs
|
||||
3. Analyze resource usage
|
||||
4. Test connectivity
|
||||
5. Verify configurations
|
||||
6. Implement fixes
|
||||
|
||||
#### Troubleshooting Commands
|
||||
```bash
|
||||
# Check logs
|
||||
journalctl -xe
|
||||
tail -f /var/log/syslog
|
||||
dmesg | tail
|
||||
|
||||
# Network troubleshooting
|
||||
ping host
|
||||
traceroute host
|
||||
curl -v http://host
|
||||
dig domain
|
||||
nslookup domain
|
||||
|
||||
# Process troubleshooting
|
||||
strace -p PID
|
||||
lsof -p PID
|
||||
iotop
|
||||
|
||||
# Disk troubleshooting
|
||||
du -sh /*
|
||||
find / -type f -size +100M
|
||||
lsof | grep deleted
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @devops-troubleshooter to diagnose server connectivity issues
|
||||
```
|
||||
|
||||
```
|
||||
Use @incident-responder to investigate system outage
|
||||
```
|
||||
|
||||
### Phase 7: Automation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `workflow-automation` - Workflow automation
|
||||
- `cicd-automation-workflow-automate` - CI/CD automation
|
||||
- `linux-shell-scripting` - Shell scripting
|
||||
|
||||
#### Actions
|
||||
1. Identify automation opportunities
|
||||
2. Design automation workflows
|
||||
3. Implement scripts
|
||||
4. Schedule with cron/systemd
|
||||
5. Monitor automation health
|
||||
|
||||
#### Cron Examples
|
||||
```bash
|
||||
# Edit crontab
|
||||
crontab -e
|
||||
|
||||
# Backup every day at 2 AM
|
||||
0 2 * * * /path/to/backup.sh
|
||||
|
||||
# Clean logs weekly
|
||||
0 3 * * 0 /path/to/cleanup.sh
|
||||
|
||||
# Monitor disk space hourly
|
||||
0 * * * * /path/to/monitor.sh
|
||||
```
|
||||
|
||||
#### Systemd Timer Example
|
||||
```ini
|
||||
# /etc/systemd/system/backup.timer
|
||||
[Unit]
|
||||
Description=Daily backup timer
|
||||
|
||||
[Timer]
|
||||
OnCalendar=daily
|
||||
Persistent=true
|
||||
|
||||
[Install]
|
||||
WantedBy=timers.target
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @workflow-automation to create automated system maintenance workflow
|
||||
```
|
||||
|
||||
## Common Troubleshooting Scenarios
|
||||
|
||||
### High CPU Usage
|
||||
```bash
|
||||
top -bn1 | head -20
|
||||
ps aux --sort=-%cpu | head -10
|
||||
pidstat 1 5
|
||||
```
|
||||
|
||||
### Memory Issues
|
||||
```bash
|
||||
free -h
|
||||
vmstat 1 10
|
||||
cat /proc/meminfo
|
||||
```
|
||||
|
||||
### Disk Space
|
||||
```bash
|
||||
df -h
|
||||
du -sh /* 2>/dev/null | sort -h
|
||||
find / -type f -size +500M 2>/dev/null
|
||||
```
|
||||
|
||||
### Network Issues
|
||||
```bash
|
||||
ip addr show
|
||||
ip route show
|
||||
ss -tulpn
|
||||
curl -v http://target
|
||||
```
|
||||
|
||||
### Service Failures
|
||||
```bash
|
||||
systemctl status service-name
|
||||
journalctl -u service-name -f
|
||||
systemctl restart service-name
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
Before completing workflow, verify:
|
||||
- [ ] All scripts pass ShellCheck
|
||||
- [ ] Tests pass with Bats
|
||||
- [ ] Error handling implemented
|
||||
- [ ] Logging configured
|
||||
- [ ] Documentation complete
|
||||
- [ ] Automation scheduled
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - Software development
|
||||
- `cloud-devops` - Cloud and DevOps
|
||||
- `security-audit` - Security testing
|
||||
- `database` - Database operations
|
||||
175
skills/postgresql-optimization/SKILL.md
Normal file
175
skills/postgresql-optimization/SKILL.md
Normal file
@@ -0,0 +1,175 @@
|
||||
---
|
||||
name: postgresql-optimization
|
||||
description: "PostgreSQL database optimization workflow for query tuning, indexing strategies, performance analysis, and production database management."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: database
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# PostgreSQL Optimization Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for PostgreSQL database optimization including query tuning, indexing strategies, performance analysis, vacuum management, and production database administration.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Optimizing slow PostgreSQL queries
|
||||
- Designing indexing strategies
|
||||
- Analyzing database performance
|
||||
- Tuning PostgreSQL configuration
|
||||
- Managing production databases
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Performance Assessment
|
||||
|
||||
#### Skills to Invoke
|
||||
- `database-optimizer` - Database optimization
|
||||
- `postgres-best-practices` - PostgreSQL best practices
|
||||
|
||||
#### Actions
|
||||
1. Check database version
|
||||
2. Review configuration
|
||||
3. Analyze slow queries
|
||||
4. Check resource usage
|
||||
5. Identify bottlenecks
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @database-optimizer to assess PostgreSQL performance
|
||||
```
|
||||
|
||||
### Phase 2: Query Analysis
|
||||
|
||||
#### Skills to Invoke
|
||||
- `sql-optimization-patterns` - SQL optimization
|
||||
- `postgres-best-practices` - PostgreSQL patterns
|
||||
|
||||
#### Actions
|
||||
1. Run EXPLAIN ANALYZE
|
||||
2. Identify scan types
|
||||
3. Check join strategies
|
||||
4. Analyze execution time
|
||||
5. Find optimization opportunities
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @sql-optimization-patterns to analyze and optimize queries
|
||||
```
|
||||
|
||||
### Phase 3: Indexing Strategy
|
||||
|
||||
#### Skills to Invoke
|
||||
- `database-design` - Index design
|
||||
- `postgresql` - PostgreSQL indexing
|
||||
|
||||
#### Actions
|
||||
1. Identify missing indexes
|
||||
2. Create B-tree indexes
|
||||
3. Add composite indexes
|
||||
4. Consider partial indexes
|
||||
5. Review index usage
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @database-design to design PostgreSQL indexing strategy
|
||||
```
|
||||
|
||||
### Phase 4: Query Optimization
|
||||
|
||||
#### Skills to Invoke
|
||||
- `sql-optimization-patterns` - Query tuning
|
||||
- `sql-pro` - SQL expertise
|
||||
|
||||
#### Actions
|
||||
1. Rewrite inefficient queries
|
||||
2. Optimize joins
|
||||
3. Add CTEs where helpful
|
||||
4. Implement pagination
|
||||
5. Test improvements
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @sql-optimization-patterns to optimize SQL queries
|
||||
```
|
||||
|
||||
### Phase 5: Configuration Tuning
|
||||
|
||||
#### Skills to Invoke
|
||||
- `postgres-best-practices` - Configuration
|
||||
- `database-admin` - Database administration
|
||||
|
||||
#### Actions
|
||||
1. Tune shared_buffers
|
||||
2. Configure work_mem
|
||||
3. Set effective_cache_size
|
||||
4. Adjust checkpoint settings
|
||||
5. Configure autovacuum
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @postgres-best-practices to tune PostgreSQL configuration
|
||||
```
|
||||
|
||||
### Phase 6: Maintenance
|
||||
|
||||
#### Skills to Invoke
|
||||
- `database-admin` - Database maintenance
|
||||
- `postgresql` - PostgreSQL maintenance
|
||||
|
||||
#### Actions
|
||||
1. Schedule VACUUM
|
||||
2. Run ANALYZE
|
||||
3. Check table bloat
|
||||
4. Monitor autovacuum
|
||||
5. Review statistics
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @database-admin to schedule PostgreSQL maintenance
|
||||
```
|
||||
|
||||
### Phase 7: Monitoring
|
||||
|
||||
#### Skills to Invoke
|
||||
- `grafana-dashboards` - Monitoring dashboards
|
||||
- `prometheus-configuration` - Metrics collection
|
||||
|
||||
#### Actions
|
||||
1. Set up monitoring
|
||||
2. Create dashboards
|
||||
3. Configure alerts
|
||||
4. Track key metrics
|
||||
5. Review trends
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @grafana-dashboards to create PostgreSQL monitoring
|
||||
```
|
||||
|
||||
## Optimization Checklist
|
||||
|
||||
- [ ] Slow queries identified
|
||||
- [ ] Indexes optimized
|
||||
- [ ] Configuration tuned
|
||||
- [ ] Maintenance scheduled
|
||||
- [ ] Monitoring active
|
||||
- [ ] Performance improved
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Query performance improved
|
||||
- [ ] Indexes effective
|
||||
- [ ] Configuration optimized
|
||||
- [ ] Maintenance automated
|
||||
- [ ] Monitoring in place
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `database` - Database operations
|
||||
- `cloud-devops` - Infrastructure
|
||||
- `performance-optimization` - Performance
|
||||
216
skills/python-fastapi-development/SKILL.md
Normal file
216
skills/python-fastapi-development/SKILL.md
Normal file
@@ -0,0 +1,216 @@
|
||||
---
|
||||
name: python-fastapi-development
|
||||
description: "Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: backend-development
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Python/FastAPI Development Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for building production-ready Python backends with FastAPI, featuring async patterns, SQLAlchemy ORM, Pydantic validation, and comprehensive API patterns.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Building new REST APIs with FastAPI
|
||||
- Creating async Python backends
|
||||
- Implementing database integration with SQLAlchemy
|
||||
- Setting up API authentication
|
||||
- Developing microservices
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Project Setup
|
||||
|
||||
#### Skills to Invoke
|
||||
- `app-builder` - Application scaffolding
|
||||
- `python-development-python-scaffold` - Python scaffolding
|
||||
- `fastapi-templates` - FastAPI templates
|
||||
- `uv-package-manager` - Package management
|
||||
|
||||
#### Actions
|
||||
1. Set up Python environment (uv/poetry)
|
||||
2. Create project structure
|
||||
3. Configure FastAPI app
|
||||
4. Set up logging
|
||||
5. Configure environment variables
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @fastapi-templates to scaffold a new FastAPI project
|
||||
```
|
||||
|
||||
```
|
||||
Use @python-development-python-scaffold to set up Python project structure
|
||||
```
|
||||
|
||||
### Phase 2: Database Setup
|
||||
|
||||
#### Skills to Invoke
|
||||
- `prisma-expert` - Prisma ORM (alternative)
|
||||
- `database-design` - Schema design
|
||||
- `postgresql` - PostgreSQL setup
|
||||
- `pydantic-models-py` - Pydantic models
|
||||
|
||||
#### Actions
|
||||
1. Design database schema
|
||||
2. Set up SQLAlchemy models
|
||||
3. Create database connection
|
||||
4. Configure migrations (Alembic)
|
||||
5. Set up session management
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @database-design to design PostgreSQL schema
|
||||
```
|
||||
|
||||
```
|
||||
Use @pydantic-models-py to create Pydantic models for API
|
||||
```
|
||||
|
||||
### Phase 3: API Routes
|
||||
|
||||
#### Skills to Invoke
|
||||
- `fastapi-router-py` - FastAPI routers
|
||||
- `api-design-principles` - API design
|
||||
- `api-patterns` - API patterns
|
||||
|
||||
#### Actions
|
||||
1. Design API endpoints
|
||||
2. Create API routers
|
||||
3. Implement CRUD operations
|
||||
4. Add request validation
|
||||
5. Configure response models
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @fastapi-router-py to create API endpoints with CRUD operations
|
||||
```
|
||||
|
||||
```
|
||||
Use @api-design-principles to design RESTful API
|
||||
```
|
||||
|
||||
### Phase 4: Authentication
|
||||
|
||||
#### Skills to Invoke
|
||||
- `auth-implementation-patterns` - Authentication
|
||||
- `api-security-best-practices` - API security
|
||||
|
||||
#### Actions
|
||||
1. Choose auth strategy (JWT, OAuth2)
|
||||
2. Implement user registration
|
||||
3. Set up login endpoints
|
||||
4. Create auth middleware
|
||||
5. Add password hashing
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @auth-implementation-patterns to implement JWT authentication
|
||||
```
|
||||
|
||||
### Phase 5: Error Handling
|
||||
|
||||
#### Skills to Invoke
|
||||
- `fastapi-pro` - FastAPI patterns
|
||||
- `error-handling-patterns` - Error handling
|
||||
|
||||
#### Actions
|
||||
1. Create custom exceptions
|
||||
2. Set up exception handlers
|
||||
3. Implement error responses
|
||||
4. Add request logging
|
||||
5. Configure error tracking
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @fastapi-pro to implement comprehensive error handling
|
||||
```
|
||||
|
||||
### Phase 6: Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `python-testing-patterns` - pytest testing
|
||||
- `api-testing-observability-api-mock` - API testing
|
||||
|
||||
#### Actions
|
||||
1. Set up pytest
|
||||
2. Create test fixtures
|
||||
3. Write unit tests
|
||||
4. Implement integration tests
|
||||
5. Configure test database
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @python-testing-patterns to write pytest tests for FastAPI
|
||||
```
|
||||
|
||||
### Phase 7: Documentation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-documenter` - API documentation
|
||||
- `openapi-spec-generation` - OpenAPI specs
|
||||
|
||||
#### Actions
|
||||
1. Configure OpenAPI schema
|
||||
2. Add endpoint documentation
|
||||
3. Create usage examples
|
||||
4. Set up API versioning
|
||||
5. Generate API docs
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-documenter to generate comprehensive API documentation
|
||||
```
|
||||
|
||||
### Phase 8: Deployment
|
||||
|
||||
#### Skills to Invoke
|
||||
- `deployment-engineer` - Deployment
|
||||
- `docker-expert` - Containerization
|
||||
|
||||
#### Actions
|
||||
1. Create Dockerfile
|
||||
2. Set up docker-compose
|
||||
3. Configure production settings
|
||||
4. Set up reverse proxy
|
||||
5. Deploy to cloud
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @docker-expert to containerize FastAPI application
|
||||
```
|
||||
|
||||
## Technology Stack
|
||||
|
||||
| Category | Technology |
|
||||
|----------|------------|
|
||||
| Framework | FastAPI |
|
||||
| Language | Python 3.11+ |
|
||||
| ORM | SQLAlchemy 2.0 |
|
||||
| Validation | Pydantic v2 |
|
||||
| Database | PostgreSQL |
|
||||
| Migrations | Alembic |
|
||||
| Auth | JWT, OAuth2 |
|
||||
| Testing | pytest |
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] All tests passing (>80% coverage)
|
||||
- [ ] Type checking passes (mypy)
|
||||
- [ ] Linting clean (ruff, black)
|
||||
- [ ] API documentation complete
|
||||
- [ ] Security scan passed
|
||||
- [ ] Performance benchmarks met
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - General development
|
||||
- `database` - Database operations
|
||||
- `security-audit` - Security testing
|
||||
- `api-development` - API patterns
|
||||
@@ -1,423 +1,197 @@
|
||||
---
|
||||
name: rag-implementation
|
||||
description: "Build Retrieval-Augmented Generation (RAG) systems for LLM applications with vector databases and semantic search. Use when implementing knowledge-grounded AI, building document Q&A systems, or int..."
|
||||
risk: unknown
|
||||
source: community
|
||||
description: "RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: ai-ml
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# RAG Implementation
|
||||
# RAG Implementation Workflow
|
||||
|
||||
Master Retrieval-Augmented Generation (RAG) to build LLM applications that provide accurate, grounded responses using external knowledge sources.
|
||||
## Overview
|
||||
|
||||
## Use this skill when
|
||||
Specialized workflow for implementing RAG (Retrieval-Augmented Generation) systems including embedding model selection, vector database setup, chunking strategies, retrieval optimization, and evaluation.
|
||||
|
||||
- Building Q&A systems over proprietary documents
|
||||
- Creating chatbots with current, factual information
|
||||
- Implementing semantic search with natural language queries
|
||||
- Reducing hallucinations with grounded responses
|
||||
- Enabling LLMs to access domain-specific knowledge
|
||||
- Building documentation assistants
|
||||
- Creating research tools with source citation
|
||||
## When to Use This Workflow
|
||||
|
||||
## Do not use this skill when
|
||||
Use this workflow when:
|
||||
- Building RAG-powered applications
|
||||
- Implementing semantic search
|
||||
- Creating knowledge-grounded AI
|
||||
- Setting up document Q&A systems
|
||||
- Optimizing retrieval quality
|
||||
|
||||
- You only need purely generative writing without retrieval
|
||||
- The dataset is too small to justify embeddings
|
||||
- You cannot store or process the source data safely
|
||||
## Workflow Phases
|
||||
|
||||
## Instructions
|
||||
### Phase 1: Requirements Analysis
|
||||
|
||||
1. Define the corpus, update cadence, and evaluation targets.
|
||||
2. Choose embedding models and vector store based on scale.
|
||||
3. Build ingestion, chunking, and retrieval with reranking.
|
||||
4. Evaluate with grounded QA metrics and monitor drift.
|
||||
#### Skills to Invoke
|
||||
- `ai-product` - AI product design
|
||||
- `rag-engineer` - RAG engineering
|
||||
|
||||
## Safety
|
||||
#### Actions
|
||||
1. Define use case
|
||||
2. Identify data sources
|
||||
3. Set accuracy requirements
|
||||
4. Determine latency targets
|
||||
5. Plan evaluation metrics
|
||||
|
||||
- Redact sensitive data and enforce access controls.
|
||||
- Avoid exposing source documents in responses when restricted.
|
||||
|
||||
## Core Components
|
||||
|
||||
### 1. Vector Databases
|
||||
**Purpose**: Store and retrieve document embeddings efficiently
|
||||
|
||||
**Options:**
|
||||
- **Pinecone**: Managed, scalable, fast queries
|
||||
- **Weaviate**: Open-source, hybrid search
|
||||
- **Milvus**: High performance, on-premise
|
||||
- **Chroma**: Lightweight, easy to use
|
||||
- **Qdrant**: Fast, filtered search
|
||||
- **FAISS**: Meta's library, local deployment
|
||||
|
||||
### 2. Embeddings
|
||||
**Purpose**: Convert text to numerical vectors for similarity search
|
||||
|
||||
**Models:**
|
||||
- **text-embedding-ada-002** (OpenAI): General purpose, 1536 dims
|
||||
- **all-MiniLM-L6-v2** (Sentence Transformers): Fast, lightweight
|
||||
- **e5-large-v2**: High quality, multilingual
|
||||
- **Instructor**: Task-specific instructions
|
||||
- **bge-large-en-v1.5**: SOTA performance
|
||||
|
||||
### 3. Retrieval Strategies
|
||||
**Approaches:**
|
||||
- **Dense Retrieval**: Semantic similarity via embeddings
|
||||
- **Sparse Retrieval**: Keyword matching (BM25, TF-IDF)
|
||||
- **Hybrid Search**: Combine dense + sparse
|
||||
- **Multi-Query**: Generate multiple query variations
|
||||
- **HyDE**: Generate hypothetical documents
|
||||
|
||||
### 4. Reranking
|
||||
**Purpose**: Improve retrieval quality by reordering results
|
||||
|
||||
**Methods:**
|
||||
- **Cross-Encoders**: BERT-based reranking
|
||||
- **Cohere Rerank**: API-based reranking
|
||||
- **Maximal Marginal Relevance (MMR)**: Diversity + relevance
|
||||
- **LLM-based**: Use LLM to score relevance
|
||||
|
||||
## Quick Start
|
||||
|
||||
```python
|
||||
from langchain.document_loaders import DirectoryLoader
|
||||
from langchain.text_splitters import RecursiveCharacterTextSplitter
|
||||
from langchain.embeddings import OpenAIEmbeddings
|
||||
from langchain.vectorstores import Chroma
|
||||
from langchain.chains import RetrievalQA
|
||||
from langchain.llms import OpenAI
|
||||
|
||||
# 1. Load documents
|
||||
loader = DirectoryLoader('./docs', glob="**/*.txt")
|
||||
documents = loader.load()
|
||||
|
||||
# 2. Split into chunks
|
||||
text_splitter = RecursiveCharacterTextSplitter(
|
||||
chunk_size=1000,
|
||||
chunk_overlap=200,
|
||||
length_function=len
|
||||
)
|
||||
chunks = text_splitter.split_documents(documents)
|
||||
|
||||
# 3. Create embeddings and vector store
|
||||
embeddings = OpenAIEmbeddings()
|
||||
vectorstore = Chroma.from_documents(chunks, embeddings)
|
||||
|
||||
# 4. Create retrieval chain
|
||||
qa_chain = RetrievalQA.from_chain_type(
|
||||
llm=OpenAI(),
|
||||
chain_type="stuff",
|
||||
retriever=vectorstore.as_retriever(search_kwargs={"k": 4}),
|
||||
return_source_documents=True
|
||||
)
|
||||
|
||||
# 5. Query
|
||||
result = qa_chain({"query": "What are the main features?"})
|
||||
print(result['result'])
|
||||
print(result['source_documents'])
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @ai-product to define RAG application requirements
|
||||
```
|
||||
|
||||
## Advanced RAG Patterns
|
||||
### Phase 2: Embedding Selection
|
||||
|
||||
### Pattern 1: Hybrid Search
|
||||
```python
|
||||
from langchain.retrievers import BM25Retriever, EnsembleRetriever
|
||||
#### Skills to Invoke
|
||||
- `embedding-strategies` - Embedding selection
|
||||
- `rag-engineer` - RAG patterns
|
||||
|
||||
# Sparse retriever (BM25)
|
||||
bm25_retriever = BM25Retriever.from_documents(chunks)
|
||||
bm25_retriever.k = 5
|
||||
#### Actions
|
||||
1. Evaluate embedding models
|
||||
2. Test domain relevance
|
||||
3. Measure embedding quality
|
||||
4. Consider cost/latency
|
||||
5. Select model
|
||||
|
||||
# Dense retriever (embeddings)
|
||||
embedding_retriever = vectorstore.as_retriever(search_kwargs={"k": 5})
|
||||
|
||||
# Combine with weights
|
||||
ensemble_retriever = EnsembleRetriever(
|
||||
retrievers=[bm25_retriever, embedding_retriever],
|
||||
weights=[0.3, 0.7]
|
||||
)
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @embedding-strategies to select optimal embedding model
|
||||
```
|
||||
|
||||
### Pattern 2: Multi-Query Retrieval
|
||||
```python
|
||||
from langchain.retrievers.multi_query import MultiQueryRetriever
|
||||
### Phase 3: Vector Database Setup
|
||||
|
||||
# Generate multiple query perspectives
|
||||
retriever = MultiQueryRetriever.from_llm(
|
||||
retriever=vectorstore.as_retriever(),
|
||||
llm=OpenAI()
|
||||
)
|
||||
#### Skills to Invoke
|
||||
- `vector-database-engineer` - Vector DB
|
||||
- `similarity-search-patterns` - Similarity search
|
||||
|
||||
# Single query → multiple variations → combined results
|
||||
results = retriever.get_relevant_documents("What is the main topic?")
|
||||
#### Actions
|
||||
1. Choose vector database
|
||||
2. Design schema
|
||||
3. Configure indexes
|
||||
4. Set up connection
|
||||
5. Test queries
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @vector-database-engineer to set up vector database
|
||||
```
|
||||
|
||||
### Pattern 3: Contextual Compression
|
||||
```python
|
||||
from langchain.retrievers import ContextualCompressionRetriever
|
||||
from langchain.retrievers.document_compressors import LLMChainExtractor
|
||||
### Phase 4: Chunking Strategy
|
||||
|
||||
compressor = LLMChainExtractor.from_llm(llm)
|
||||
#### Skills to Invoke
|
||||
- `rag-engineer` - Chunking strategies
|
||||
- `rag-implementation` - RAG implementation
|
||||
|
||||
compression_retriever = ContextualCompressionRetriever(
|
||||
base_compressor=compressor,
|
||||
base_retriever=vectorstore.as_retriever()
|
||||
)
|
||||
#### Actions
|
||||
1. Choose chunk size
|
||||
2. Implement chunking
|
||||
3. Add overlap handling
|
||||
4. Create metadata
|
||||
5. Test retrieval quality
|
||||
|
||||
# Returns only relevant parts of documents
|
||||
compressed_docs = compression_retriever.get_relevant_documents("query")
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @rag-engineer to implement chunking strategy
|
||||
```
|
||||
|
||||
### Pattern 4: Parent Document Retriever
|
||||
```python
|
||||
from langchain.retrievers import ParentDocumentRetriever
|
||||
from langchain.storage import InMemoryStore
|
||||
### Phase 5: Retrieval Implementation
|
||||
|
||||
# Store for parent documents
|
||||
store = InMemoryStore()
|
||||
#### Skills to Invoke
|
||||
- `similarity-search-patterns` - Similarity search
|
||||
- `hybrid-search-implementation` - Hybrid search
|
||||
|
||||
# Small chunks for retrieval, large chunks for context
|
||||
child_splitter = RecursiveCharacterTextSplitter(chunk_size=400)
|
||||
parent_splitter = RecursiveCharacterTextSplitter(chunk_size=2000)
|
||||
#### Actions
|
||||
1. Implement vector search
|
||||
2. Add keyword search
|
||||
3. Configure hybrid search
|
||||
4. Set up reranking
|
||||
5. Optimize latency
|
||||
|
||||
retriever = ParentDocumentRetriever(
|
||||
vectorstore=vectorstore,
|
||||
docstore=store,
|
||||
child_splitter=child_splitter,
|
||||
parent_splitter=parent_splitter
|
||||
)
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @similarity-search-patterns to implement retrieval
|
||||
```
|
||||
|
||||
## Document Chunking Strategies
|
||||
|
||||
### Recursive Character Text Splitter
|
||||
```python
|
||||
from langchain.text_splitters import RecursiveCharacterTextSplitter
|
||||
|
||||
splitter = RecursiveCharacterTextSplitter(
|
||||
chunk_size=1000,
|
||||
chunk_overlap=200,
|
||||
length_function=len,
|
||||
separators=["\n\n", "\n", " ", ""] # Try these in order
|
||||
)
|
||||
```
|
||||
Use @hybrid-search-implementation to add hybrid search
|
||||
```
|
||||
|
||||
### Token-Based Splitting
|
||||
```python
|
||||
from langchain.text_splitters import TokenTextSplitter
|
||||
### Phase 6: LLM Integration
|
||||
|
||||
splitter = TokenTextSplitter(
|
||||
chunk_size=512,
|
||||
chunk_overlap=50
|
||||
)
|
||||
#### Skills to Invoke
|
||||
- `llm-application-dev-ai-assistant` - LLM integration
|
||||
- `llm-application-dev-prompt-optimize` - Prompt optimization
|
||||
|
||||
#### Actions
|
||||
1. Select LLM provider
|
||||
2. Design prompt template
|
||||
3. Implement context injection
|
||||
4. Add citation handling
|
||||
5. Test generation quality
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @llm-application-dev-ai-assistant to integrate LLM
|
||||
```
|
||||
|
||||
### Semantic Chunking
|
||||
```python
|
||||
from langchain.text_splitters import SemanticChunker
|
||||
### Phase 7: Caching
|
||||
|
||||
splitter = SemanticChunker(
|
||||
embeddings=OpenAIEmbeddings(),
|
||||
breakpoint_threshold_type="percentile"
|
||||
)
|
||||
#### Skills to Invoke
|
||||
- `prompt-caching` - Prompt caching
|
||||
- `rag-engineer` - RAG optimization
|
||||
|
||||
#### Actions
|
||||
1. Implement response caching
|
||||
2. Set up embedding cache
|
||||
3. Configure TTL
|
||||
4. Add cache invalidation
|
||||
5. Monitor hit rates
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @prompt-caching to implement RAG caching
|
||||
```
|
||||
|
||||
### Markdown Header Splitter
|
||||
```python
|
||||
from langchain.text_splitters import MarkdownHeaderTextSplitter
|
||||
### Phase 8: Evaluation
|
||||
|
||||
headers_to_split_on = [
|
||||
("#", "Header 1"),
|
||||
("##", "Header 2"),
|
||||
("###", "Header 3"),
|
||||
]
|
||||
#### Skills to Invoke
|
||||
- `llm-evaluation` - LLM evaluation
|
||||
- `evaluation` - AI evaluation
|
||||
|
||||
splitter = MarkdownHeaderTextSplitter(headers_to_split_on=headers_to_split_on)
|
||||
#### Actions
|
||||
1. Define evaluation metrics
|
||||
2. Create test dataset
|
||||
3. Measure retrieval accuracy
|
||||
4. Evaluate generation quality
|
||||
5. Iterate on improvements
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @llm-evaluation to evaluate RAG system
|
||||
```
|
||||
|
||||
## Vector Store Configurations
|
||||
## RAG Architecture
|
||||
|
||||
### Pinecone
|
||||
```python
|
||||
import pinecone
|
||||
from langchain.vectorstores import Pinecone
|
||||
|
||||
pinecone.init(api_key="your-api-key", environment="us-west1-gcp")
|
||||
|
||||
index = pinecone.Index("your-index-name")
|
||||
|
||||
vectorstore = Pinecone(index, embeddings.embed_query, "text")
|
||||
```
|
||||
User Query -> Embedding -> Vector Search -> Retrieved Docs -> LLM -> Response
|
||||
| | | |
|
||||
Model Vector DB Chunk Store Prompt + Context
|
||||
```
|
||||
|
||||
### Weaviate
|
||||
```python
|
||||
import weaviate
|
||||
from langchain.vectorstores import Weaviate
|
||||
## Quality Gates
|
||||
|
||||
client = weaviate.Client("http://localhost:8080")
|
||||
- [ ] Embedding model selected
|
||||
- [ ] Vector DB configured
|
||||
- [ ] Chunking implemented
|
||||
- [ ] Retrieval working
|
||||
- [ ] LLM integrated
|
||||
- [ ] Evaluation passing
|
||||
|
||||
vectorstore = Weaviate(client, "Document", "content", embeddings)
|
||||
```
|
||||
## Related Workflow Bundles
|
||||
|
||||
### Chroma (Local)
|
||||
```python
|
||||
from langchain.vectorstores import Chroma
|
||||
|
||||
vectorstore = Chroma(
|
||||
collection_name="my_collection",
|
||||
embedding_function=embeddings,
|
||||
persist_directory="./chroma_db"
|
||||
)
|
||||
```
|
||||
|
||||
## Retrieval Optimization
|
||||
|
||||
### 1. Metadata Filtering
|
||||
```python
|
||||
# Add metadata during indexing
|
||||
chunks_with_metadata = []
|
||||
for i, chunk in enumerate(chunks):
|
||||
chunk.metadata = {
|
||||
"source": chunk.metadata.get("source"),
|
||||
"page": i,
|
||||
"category": determine_category(chunk.page_content)
|
||||
}
|
||||
chunks_with_metadata.append(chunk)
|
||||
|
||||
# Filter during retrieval
|
||||
results = vectorstore.similarity_search(
|
||||
"query",
|
||||
filter={"category": "technical"},
|
||||
k=5
|
||||
)
|
||||
```
|
||||
|
||||
### 2. Maximal Marginal Relevance
|
||||
```python
|
||||
# Balance relevance with diversity
|
||||
results = vectorstore.max_marginal_relevance_search(
|
||||
"query",
|
||||
k=5,
|
||||
fetch_k=20, # Fetch 20, return top 5 diverse
|
||||
lambda_mult=0.5 # 0=max diversity, 1=max relevance
|
||||
)
|
||||
```
|
||||
|
||||
### 3. Reranking with Cross-Encoder
|
||||
```python
|
||||
from sentence_transformers import CrossEncoder
|
||||
|
||||
reranker = CrossEncoder('cross-encoder/ms-marco-MiniLM-L-6-v2')
|
||||
|
||||
# Get initial results
|
||||
candidates = vectorstore.similarity_search("query", k=20)
|
||||
|
||||
# Rerank
|
||||
pairs = [[query, doc.page_content] for doc in candidates]
|
||||
scores = reranker.predict(pairs)
|
||||
|
||||
# Sort by score and take top k
|
||||
reranked = sorted(zip(candidates, scores), key=lambda x: x[1], reverse=True)[:5]
|
||||
```
|
||||
|
||||
## Prompt Engineering for RAG
|
||||
|
||||
### Contextual Prompt
|
||||
```python
|
||||
prompt_template = """Use the following context to answer the question. If you cannot answer based on the context, say "I don't have enough information."
|
||||
|
||||
Context:
|
||||
{context}
|
||||
|
||||
Question: {question}
|
||||
|
||||
Answer:"""
|
||||
```
|
||||
|
||||
### With Citations
|
||||
```python
|
||||
prompt_template = """Answer the question based on the context below. Include citations using [1], [2], etc.
|
||||
|
||||
Context:
|
||||
{context}
|
||||
|
||||
Question: {question}
|
||||
|
||||
Answer (with citations):"""
|
||||
```
|
||||
|
||||
### With Confidence
|
||||
```python
|
||||
prompt_template = """Answer the question using the context. Provide a confidence score (0-100%) for your answer.
|
||||
|
||||
Context:
|
||||
{context}
|
||||
|
||||
Question: {question}
|
||||
|
||||
Answer:
|
||||
Confidence:"""
|
||||
```
|
||||
|
||||
## Evaluation Metrics
|
||||
|
||||
```python
|
||||
def evaluate_rag_system(qa_chain, test_cases):
|
||||
metrics = {
|
||||
'accuracy': [],
|
||||
'retrieval_quality': [],
|
||||
'groundedness': []
|
||||
}
|
||||
|
||||
for test in test_cases:
|
||||
result = qa_chain({"query": test['question']})
|
||||
|
||||
# Check if answer matches expected
|
||||
accuracy = calculate_accuracy(result['result'], test['expected'])
|
||||
metrics['accuracy'].append(accuracy)
|
||||
|
||||
# Check if relevant docs were retrieved
|
||||
retrieval_quality = evaluate_retrieved_docs(
|
||||
result['source_documents'],
|
||||
test['relevant_docs']
|
||||
)
|
||||
metrics['retrieval_quality'].append(retrieval_quality)
|
||||
|
||||
# Check if answer is grounded in context
|
||||
groundedness = check_groundedness(
|
||||
result['result'],
|
||||
result['source_documents']
|
||||
)
|
||||
metrics['groundedness'].append(groundedness)
|
||||
|
||||
return {k: sum(v)/len(v) for k, v in metrics.items()}
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
- **references/vector-databases.md**: Detailed comparison of vector DBs
|
||||
- **references/embeddings.md**: Embedding model selection guide
|
||||
- **references/retrieval-strategies.md**: Advanced retrieval techniques
|
||||
- **references/reranking.md**: Reranking methods and when to use them
|
||||
- **references/context-window.md**: Managing context limits
|
||||
- **assets/vector-store-config.yaml**: Configuration templates
|
||||
- **assets/retriever-pipeline.py**: Complete RAG pipeline
|
||||
- **assets/embedding-models.md**: Model comparison and benchmarks
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. **Chunk Size**: Balance between context and specificity (500-1000 tokens)
|
||||
2. **Overlap**: Use 10-20% overlap to preserve context at boundaries
|
||||
3. **Metadata**: Include source, page, timestamp for filtering and debugging
|
||||
4. **Hybrid Search**: Combine semantic and keyword search for best results
|
||||
5. **Reranking**: Improve top results with cross-encoder
|
||||
6. **Citations**: Always return source documents for transparency
|
||||
7. **Evaluation**: Continuously test retrieval quality and answer accuracy
|
||||
8. **Monitoring**: Track retrieval metrics in production
|
||||
|
||||
## Common Issues
|
||||
|
||||
- **Poor Retrieval**: Check embedding quality, chunk size, query formulation
|
||||
- **Irrelevant Results**: Add metadata filtering, use hybrid search, rerank
|
||||
- **Missing Information**: Ensure documents are properly indexed
|
||||
- **Slow Queries**: Optimize vector store, use caching, reduce k
|
||||
- **Hallucinations**: Improve grounding prompt, add verification step
|
||||
- `ai-ml` - AI/ML development
|
||||
- `ai-agent-development` - AI agents
|
||||
- `database` - Vector databases
|
||||
|
||||
229
skills/react-nextjs-development/SKILL.md
Normal file
229
skills/react-nextjs-development/SKILL.md
Normal file
@@ -0,0 +1,229 @@
|
||||
---
|
||||
name: react-nextjs-development
|
||||
description: "React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: frontend-development
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# React/Next.js Development Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for building React and Next.js 14+ applications with modern patterns including App Router, Server Components, TypeScript, and Tailwind CSS.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Building new React applications
|
||||
- Creating Next.js 14+ projects with App Router
|
||||
- Implementing Server Components
|
||||
- Setting up TypeScript with React
|
||||
- Styling with Tailwind CSS
|
||||
- Building full-stack Next.js applications
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Project Setup
|
||||
|
||||
#### Skills to Invoke
|
||||
- `app-builder` - Application scaffolding
|
||||
- `senior-fullstack` - Full-stack guidance
|
||||
- `nextjs-app-router-patterns` - Next.js 14+ patterns
|
||||
- `typescript-pro` - TypeScript setup
|
||||
|
||||
#### Actions
|
||||
1. Choose project type (React SPA, Next.js app)
|
||||
2. Select build tool (Vite, Next.js, Create React App)
|
||||
3. Scaffold project structure
|
||||
4. Configure TypeScript
|
||||
5. Set up ESLint and Prettier
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @app-builder to scaffold a new Next.js 14 project with App Router
|
||||
```
|
||||
|
||||
```
|
||||
Use @nextjs-app-router-patterns to set up Server Components
|
||||
```
|
||||
|
||||
### Phase 2: Component Architecture
|
||||
|
||||
#### Skills to Invoke
|
||||
- `frontend-developer` - Component development
|
||||
- `react-patterns` - React patterns
|
||||
- `react-state-management` - State management
|
||||
- `react-ui-patterns` - UI patterns
|
||||
|
||||
#### Actions
|
||||
1. Design component hierarchy
|
||||
2. Create base components
|
||||
3. Implement layout components
|
||||
4. Set up state management
|
||||
5. Create custom hooks
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @frontend-developer to create reusable React components
|
||||
```
|
||||
|
||||
```
|
||||
Use @react-patterns to implement proper component composition
|
||||
```
|
||||
|
||||
```
|
||||
Use @react-state-management to set up Zustand store
|
||||
```
|
||||
|
||||
### Phase 3: Styling and Design
|
||||
|
||||
#### Skills to Invoke
|
||||
- `frontend-design` - UI design
|
||||
- `tailwind-patterns` - Tailwind CSS
|
||||
- `tailwind-design-system` - Design system
|
||||
- `core-components` - Component library
|
||||
|
||||
#### Actions
|
||||
1. Set up Tailwind CSS
|
||||
2. Configure design tokens
|
||||
3. Create utility classes
|
||||
4. Build component styles
|
||||
5. Implement responsive design
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @tailwind-patterns to style components with Tailwind CSS v4
|
||||
```
|
||||
|
||||
```
|
||||
Use @frontend-design to create a modern dashboard UI
|
||||
```
|
||||
|
||||
### Phase 4: Data Fetching
|
||||
|
||||
#### Skills to Invoke
|
||||
- `nextjs-app-router-patterns` - Server Components
|
||||
- `react-state-management` - React Query
|
||||
- `api-patterns` - API integration
|
||||
|
||||
#### Actions
|
||||
1. Implement Server Components
|
||||
2. Set up React Query/SWR
|
||||
3. Create API client
|
||||
4. Handle loading states
|
||||
5. Implement error boundaries
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @nextjs-app-router-patterns to implement Server Components data fetching
|
||||
```
|
||||
|
||||
### Phase 5: Routing and Navigation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `nextjs-app-router-patterns` - App Router
|
||||
- `nextjs-best-practices` - Next.js patterns
|
||||
|
||||
#### Actions
|
||||
1. Set up file-based routing
|
||||
2. Create dynamic routes
|
||||
3. Implement nested routes
|
||||
4. Add route guards
|
||||
5. Configure redirects
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @nextjs-app-router-patterns to set up parallel routes and intercepting routes
|
||||
```
|
||||
|
||||
### Phase 6: Forms and Validation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `frontend-developer` - Form development
|
||||
- `typescript-advanced-types` - Type validation
|
||||
- `react-ui-patterns` - Form patterns
|
||||
|
||||
#### Actions
|
||||
1. Choose form library (React Hook Form, Formik)
|
||||
2. Set up validation (Zod, Yup)
|
||||
3. Create form components
|
||||
4. Handle submissions
|
||||
5. Implement error handling
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @frontend-developer to create forms with React Hook Form and Zod
|
||||
```
|
||||
|
||||
### Phase 7: Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `javascript-testing-patterns` - Jest/Vitest
|
||||
- `playwright-skill` - E2E testing
|
||||
- `e2e-testing-patterns` - E2E patterns
|
||||
|
||||
#### Actions
|
||||
1. Set up testing framework
|
||||
2. Write unit tests
|
||||
3. Create component tests
|
||||
4. Implement E2E tests
|
||||
5. Configure CI integration
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @javascript-testing-patterns to write Vitest tests
|
||||
```
|
||||
|
||||
```
|
||||
Use @playwright-skill to create E2E tests for critical flows
|
||||
```
|
||||
|
||||
### Phase 8: Build and Deployment
|
||||
|
||||
#### Skills to Invoke
|
||||
- `vercel-deployment` - Vercel deployment
|
||||
- `vercel-deploy-claimable` - Vercel deployment
|
||||
- `web-performance-optimization` - Performance
|
||||
|
||||
#### Actions
|
||||
1. Configure build settings
|
||||
2. Optimize bundle size
|
||||
3. Set up environment variables
|
||||
4. Deploy to Vercel
|
||||
5. Configure preview deployments
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @vercel-deployment to deploy Next.js app to production
|
||||
```
|
||||
|
||||
## Technology Stack
|
||||
|
||||
| Category | Technology |
|
||||
|----------|------------|
|
||||
| Framework | Next.js 14+, React 18+ |
|
||||
| Language | TypeScript 5+ |
|
||||
| Styling | Tailwind CSS v4 |
|
||||
| State | Zustand, React Query |
|
||||
| Forms | React Hook Form, Zod |
|
||||
| Testing | Vitest, Playwright |
|
||||
| Deployment | Vercel |
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] TypeScript compiles without errors
|
||||
- [ ] All tests passing
|
||||
- [ ] Linting clean
|
||||
- [ ] Performance metrics met (LCP, CLS, FID)
|
||||
- [ ] Accessibility checked (WCAG 2.1)
|
||||
- [ ] Responsive design verified
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - General development
|
||||
- `testing-qa` - Testing workflow
|
||||
- `documentation` - Documentation
|
||||
- `typescript-development` - TypeScript patterns
|
||||
218
skills/security-audit/SKILL.md
Normal file
218
skills/security-audit/SKILL.md
Normal file
@@ -0,0 +1,218 @@
|
||||
---
|
||||
name: security-audit
|
||||
description: "Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: security
|
||||
category: workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Security Auditing Workflow Bundle
|
||||
|
||||
## Overview
|
||||
|
||||
Comprehensive security auditing workflow for web applications, APIs, and infrastructure. This bundle orchestrates skills for penetration testing, vulnerability assessment, security scanning, and remediation.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Performing security audits on web applications
|
||||
- Testing API security
|
||||
- Conducting penetration tests
|
||||
- Scanning for vulnerabilities
|
||||
- Hardening application security
|
||||
- Compliance security assessments
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Reconnaissance
|
||||
|
||||
#### Skills to Invoke
|
||||
- `scanning-tools` - Security scanning
|
||||
- `shodan-reconnaissance` - Shodan searches
|
||||
- `top-web-vulnerabilities` - OWASP Top 10
|
||||
|
||||
#### Actions
|
||||
1. Identify target scope
|
||||
2. Gather intelligence
|
||||
3. Map attack surface
|
||||
4. Identify technologies
|
||||
5. Document findings
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @scanning-tools to perform initial reconnaissance
|
||||
```
|
||||
|
||||
```
|
||||
Use @shodan-reconnaissance to find exposed services
|
||||
```
|
||||
|
||||
### Phase 2: Vulnerability Scanning
|
||||
|
||||
#### Skills to Invoke
|
||||
- `vulnerability-scanner` - Vulnerability analysis
|
||||
- `security-scanning-security-sast` - Static analysis
|
||||
- `security-scanning-security-dependencies` - Dependency scanning
|
||||
|
||||
#### Actions
|
||||
1. Run automated scanners
|
||||
2. Perform static analysis
|
||||
3. Scan dependencies
|
||||
4. Identify misconfigurations
|
||||
5. Document vulnerabilities
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @vulnerability-scanner to scan for OWASP Top 10 vulnerabilities
|
||||
```
|
||||
|
||||
```
|
||||
Use @security-scanning-security-dependencies to audit dependencies
|
||||
```
|
||||
|
||||
### Phase 3: Web Application Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `top-web-vulnerabilities` - OWASP vulnerabilities
|
||||
- `sql-injection-testing` - SQL injection
|
||||
- `xss-html-injection` - XSS testing
|
||||
- `broken-authentication` - Authentication testing
|
||||
- `idor-testing` - IDOR testing
|
||||
- `file-path-traversal` - Path traversal
|
||||
- `burp-suite-testing` - Burp Suite testing
|
||||
|
||||
#### Actions
|
||||
1. Test for injection flaws
|
||||
2. Test authentication mechanisms
|
||||
3. Test session management
|
||||
4. Test access controls
|
||||
5. Test input validation
|
||||
6. Test security headers
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @sql-injection-testing to test for SQL injection vulnerabilities
|
||||
```
|
||||
|
||||
```
|
||||
Use @xss-html-injection to test for cross-site scripting
|
||||
```
|
||||
|
||||
```
|
||||
Use @broken-authentication to test authentication security
|
||||
```
|
||||
|
||||
### Phase 4: API Security Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-fuzzing-bug-bounty` - API fuzzing
|
||||
- `api-security-best-practices` - API security
|
||||
|
||||
#### Actions
|
||||
1. Enumerate API endpoints
|
||||
2. Test authentication/authorization
|
||||
3. Test rate limiting
|
||||
4. Test input validation
|
||||
5. Test error handling
|
||||
6. Document API vulnerabilities
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-fuzzing-bug-bounty to fuzz API endpoints
|
||||
```
|
||||
|
||||
### Phase 5: Penetration Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `pentest-commands` - Penetration testing commands
|
||||
- `pentest-checklist` - Pentest planning
|
||||
- `ethical-hacking-methodology` - Ethical hacking
|
||||
- `metasploit-framework` - Metasploit
|
||||
|
||||
#### Actions
|
||||
1. Plan penetration test
|
||||
2. Execute attack scenarios
|
||||
3. Exploit vulnerabilities
|
||||
4. Document proof of concept
|
||||
5. Assess impact
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @pentest-checklist to plan penetration test
|
||||
```
|
||||
|
||||
```
|
||||
Use @pentest-commands to execute penetration testing
|
||||
```
|
||||
|
||||
### Phase 6: Security Hardening
|
||||
|
||||
#### Skills to Invoke
|
||||
- `security-scanning-security-hardening` - Security hardening
|
||||
- `auth-implementation-patterns` - Authentication
|
||||
- `api-security-best-practices` - API security
|
||||
|
||||
#### Actions
|
||||
1. Implement security controls
|
||||
2. Configure security headers
|
||||
3. Set up authentication
|
||||
4. Implement authorization
|
||||
5. Configure logging
|
||||
6. Apply patches
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @security-scanning-security-hardening to harden application security
|
||||
```
|
||||
|
||||
### Phase 7: Reporting
|
||||
|
||||
#### Skills to Invoke
|
||||
- `reporting-standards` - Security reporting
|
||||
|
||||
#### Actions
|
||||
1. Document findings
|
||||
2. Assess risk levels
|
||||
3. Provide remediation steps
|
||||
4. Create executive summary
|
||||
5. Generate technical report
|
||||
|
||||
## Security Testing Checklist
|
||||
|
||||
### OWASP Top 10
|
||||
- [ ] Injection (SQL, NoSQL, OS, LDAP)
|
||||
- [ ] Broken Authentication
|
||||
- [ ] Sensitive Data Exposure
|
||||
- [ ] XML External Entities (XXE)
|
||||
- [ ] Broken Access Control
|
||||
- [ ] Security Misconfiguration
|
||||
- [ ] Cross-Site Scripting (XSS)
|
||||
- [ ] Insecure Deserialization
|
||||
- [ ] Using Components with Known Vulnerabilities
|
||||
- [ ] Insufficient Logging & Monitoring
|
||||
|
||||
### API Security
|
||||
- [ ] Authentication mechanisms
|
||||
- [ ] Authorization checks
|
||||
- [ ] Rate limiting
|
||||
- [ ] Input validation
|
||||
- [ ] Error handling
|
||||
- [ ] Security headers
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] All planned tests executed
|
||||
- [ ] Vulnerabilities documented
|
||||
- [ ] Proof of concepts captured
|
||||
- [ ] Risk assessments completed
|
||||
- [ ] Remediation steps provided
|
||||
- [ ] Report generated
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - Secure development practices
|
||||
- `wordpress` - WordPress security
|
||||
- `cloud-devops` - Cloud security
|
||||
- `testing-qa` - Security testing
|
||||
121
skills/shader-programming-glsl/SKILL.md
Normal file
121
skills/shader-programming-glsl/SKILL.md
Normal file
@@ -0,0 +1,121 @@
|
||||
---
|
||||
name: shader-programming-glsl
|
||||
description: Expert guide for writing efficient GLSL shaders (Vertex/Fragment) for web and game engines, covering syntax, uniforms, and common effects.
|
||||
risk: safe
|
||||
source: community
|
||||
---
|
||||
|
||||
# Shader Programming GLSL
|
||||
|
||||
## Overview
|
||||
|
||||
A comprehensive guide to writing GPU shaders using GLSL (OpenGL Shading Language). Learn syntax, uniforms, varying variables, and key mathematical concepts like swizzling and vector operations for visual effects.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
- Use when creating custom visual effects in WebGL, Three.js, or game engines.
|
||||
- Use when optimizing graphics rendering performance.
|
||||
- Use when implementing post-processing effects (blur, bloom, color correction).
|
||||
- Use when procedurally generating textures or geometry on the GPU.
|
||||
|
||||
## Step-by-Step Guide
|
||||
|
||||
### 1. Structure: Vertex vs. Fragment
|
||||
|
||||
Understand the pipeline:
|
||||
- **Vertex Shader**: Transforms 3D coordinates to 2D screen space (`gl_Position`).
|
||||
- **Fragment Shader**: Colors individual pixels (`gl_FragColor`).
|
||||
|
||||
```glsl
|
||||
// Vertex Shader (basic)
|
||||
attribute vec3 position;
|
||||
uniform mat4 modelViewMatrix;
|
||||
uniform mat4 projectionMatrix;
|
||||
|
||||
void main() {
|
||||
gl_Position = projectionMatrix * modelViewMatrix * vec4(position, 1.0);
|
||||
}
|
||||
```
|
||||
|
||||
```glsl
|
||||
// Fragment Shader (basic)
|
||||
uniform vec3 color;
|
||||
|
||||
void main() {
|
||||
gl_FragColor = vec4(color, 1.0);
|
||||
}
|
||||
```
|
||||
|
||||
### 2. Uniforms and Varyings
|
||||
|
||||
- `uniform`: Data constant for all vertices/fragments (passed from CPU).
|
||||
- `varying`: Data interpolated from vertex to fragment shader.
|
||||
|
||||
```glsl
|
||||
// Passing UV coordinates
|
||||
varying vec2 vUv;
|
||||
|
||||
// In Vertex Shader
|
||||
void main() {
|
||||
vUv = uv;
|
||||
gl_Position = projectionMatrix * modelViewMatrix * vec4(position, 1.0);
|
||||
}
|
||||
|
||||
// In Fragment Shader
|
||||
void main() {
|
||||
// Gradient based on UV
|
||||
gl_FragColor = vec4(vUv.x, vUv.y, 1.0, 1.0);
|
||||
}
|
||||
```
|
||||
|
||||
### 3. Swizzling & Vector Math
|
||||
|
||||
Access vector components freely: `vec4 color = vec4(1.0, 0.5, 0.0, 1.0);`
|
||||
- `color.rgb` -> `vec3(1.0, 0.5, 0.0)`
|
||||
- `color.zyx` -> `vec3(0.0, 0.5, 1.0)` (reordering)
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Simple Raymarching (SDF Sphere)
|
||||
|
||||
```glsl
|
||||
float sdSphere(vec3 p, float s) {
|
||||
return length(p) - s;
|
||||
}
|
||||
|
||||
void mainImage(out vec4 fragColor, in vec2 fragCoord) {
|
||||
vec2 uv = (fragCoord - 0.5 * iResolution.xy) / iResolution.y;
|
||||
vec3 ro = vec3(0.0, 0.0, -3.0); // Ray Origin
|
||||
vec3 rd = normalize(vec3(uv, 1.0)); // Ray Direction
|
||||
|
||||
float t = 0.0;
|
||||
for(int i = 0; i < 64; i++) {
|
||||
vec3 p = ro + rd * t;
|
||||
float d = sdSphere(p, 1.0); // Sphere radius 1.0
|
||||
if(d < 0.001) break;
|
||||
t += d;
|
||||
}
|
||||
|
||||
vec3 col = vec3(0.0);
|
||||
if(t < 10.0) {
|
||||
vec3 p = ro + rd * t;
|
||||
vec3 normal = normalize(p);
|
||||
col = normal * 0.5 + 0.5; // Color by normal
|
||||
}
|
||||
|
||||
fragColor = vec4(col, 1.0);
|
||||
}
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
- ✅ **Do:** Use `mix()` for linear interpolation instead of manual math.
|
||||
- ✅ **Do:** Use `step()` and `smoothstep()` for thresholding and soft edges (avoid `if` branches).
|
||||
- ✅ **Do:** Pack data into vectors (`vec4`) to minimize memory access.
|
||||
- ❌ **Don't:** Use heavy branching (`if-else`) inside loops if possible; it hurts GPU parallelism.
|
||||
- ❌ **Don't:** Calculate constant values inside the shader; pre-calculate them on the CPU (uniforms).
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
**Problem:** Shader compiles but screen is black.
|
||||
**Solution:** Check if `gl_Position.w` is correct (usually 1.0). Check if uniforms are actually being set from the host application. Verify UV coordinates are within [0, 1].
|
||||
164
skills/terraform-infrastructure/SKILL.md
Normal file
164
skills/terraform-infrastructure/SKILL.md
Normal file
@@ -0,0 +1,164 @@
|
||||
---
|
||||
name: terraform-infrastructure
|
||||
description: "Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: cloud-devops
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Terraform Infrastructure Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for infrastructure as code using Terraform including resource provisioning, module creation, state management, and multi-environment deployments.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Provisioning cloud infrastructure
|
||||
- Creating Terraform modules
|
||||
- Managing multi-environment infra
|
||||
- Implementing IaC best practices
|
||||
- Setting up Terraform workflows
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Terraform Setup
|
||||
|
||||
#### Skills to Invoke
|
||||
- `terraform-skill` - Terraform basics
|
||||
- `terraform-specialist` - Advanced Terraform
|
||||
|
||||
#### Actions
|
||||
1. Initialize Terraform
|
||||
2. Configure backend
|
||||
3. Set up providers
|
||||
4. Configure variables
|
||||
5. Create outputs
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @terraform-skill to set up Terraform project
|
||||
```
|
||||
|
||||
### Phase 2: Resource Provisioning
|
||||
|
||||
#### Skills to Invoke
|
||||
- `terraform-module-library` - Terraform modules
|
||||
- `cloud-architect` - Cloud architecture
|
||||
|
||||
#### Actions
|
||||
1. Design infrastructure
|
||||
2. Create resource definitions
|
||||
3. Configure networking
|
||||
4. Set up compute
|
||||
5. Add storage
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @terraform-module-library to provision cloud resources
|
||||
```
|
||||
|
||||
### Phase 3: Module Creation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `terraform-module-library` - Module creation
|
||||
|
||||
#### Actions
|
||||
1. Design module interface
|
||||
2. Create module structure
|
||||
3. Define variables/outputs
|
||||
4. Add documentation
|
||||
5. Test module
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @terraform-module-library to create reusable Terraform module
|
||||
```
|
||||
|
||||
### Phase 4: State Management
|
||||
|
||||
#### Skills to Invoke
|
||||
- `terraform-specialist` - State management
|
||||
|
||||
#### Actions
|
||||
1. Configure remote backend
|
||||
2. Set up state locking
|
||||
3. Implement workspaces
|
||||
4. Configure state access
|
||||
5. Set up backup
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @terraform-specialist to configure Terraform state
|
||||
```
|
||||
|
||||
### Phase 5: Multi-Environment
|
||||
|
||||
#### Skills to Invoke
|
||||
- `terraform-specialist` - Multi-environment
|
||||
|
||||
#### Actions
|
||||
1. Design environment structure
|
||||
2. Create environment configs
|
||||
3. Set up variable files
|
||||
4. Configure isolation
|
||||
5. Test deployments
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @terraform-specialist to set up multi-environment Terraform
|
||||
```
|
||||
|
||||
### Phase 6: CI/CD Integration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `cicd-automation-workflow-automate` - CI/CD
|
||||
- `github-actions-templates` - GitHub Actions
|
||||
|
||||
#### Actions
|
||||
1. Create CI pipeline
|
||||
2. Configure plan/apply
|
||||
3. Set up approvals
|
||||
4. Add validation
|
||||
5. Test pipeline
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @cicd-automation-workflow-automate to create Terraform CI/CD
|
||||
```
|
||||
|
||||
### Phase 7: Security
|
||||
|
||||
#### Skills to Invoke
|
||||
- `secrets-management` - Secrets management
|
||||
- `terraform-specialist` - Security
|
||||
|
||||
#### Actions
|
||||
1. Configure secrets
|
||||
2. Set up encryption
|
||||
3. Implement policies
|
||||
4. Add compliance
|
||||
5. Audit access
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @secrets-management to secure Terraform secrets
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Resources provisioned
|
||||
- [ ] Modules working
|
||||
- [ ] State configured
|
||||
- [ ] Multi-env tested
|
||||
- [ ] CI/CD working
|
||||
- [ ] Security verified
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `cloud-devops` - Cloud/DevOps
|
||||
- `kubernetes-deployment` - Kubernetes
|
||||
- `aws-infrastructure` - AWS specific
|
||||
231
skills/testing-qa/SKILL.md
Normal file
231
skills/testing-qa/SKILL.md
Normal file
@@ -0,0 +1,231 @@
|
||||
---
|
||||
name: testing-qa
|
||||
description: "Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: quality-assurance
|
||||
category: workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Testing/QA Workflow Bundle
|
||||
|
||||
## Overview
|
||||
|
||||
Comprehensive testing and quality assurance workflow covering unit tests, integration tests, E2E tests, browser automation, and quality gates for production-ready software.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Setting up testing infrastructure
|
||||
- Writing unit and integration tests
|
||||
- Implementing E2E tests
|
||||
- Automating browser testing
|
||||
- Establishing quality gates
|
||||
- Performing code review
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Test Strategy
|
||||
|
||||
#### Skills to Invoke
|
||||
- `test-automator` - Test automation
|
||||
- `test-driven-development` - TDD
|
||||
|
||||
#### Actions
|
||||
1. Define testing strategy
|
||||
2. Choose testing frameworks
|
||||
3. Plan test coverage
|
||||
4. Set up test infrastructure
|
||||
5. Configure CI integration
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @test-automator to design testing strategy
|
||||
```
|
||||
|
||||
```
|
||||
Use @test-driven-development to implement TDD workflow
|
||||
```
|
||||
|
||||
### Phase 2: Unit Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `javascript-testing-patterns` - Jest/Vitest
|
||||
- `python-testing-patterns` - pytest
|
||||
- `unit-testing-test-generate` - Test generation
|
||||
- `tdd-orchestrator` - TDD orchestration
|
||||
|
||||
#### Actions
|
||||
1. Write unit tests
|
||||
2. Set up test fixtures
|
||||
3. Configure mocking
|
||||
4. Measure coverage
|
||||
5. Integrate with CI
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @javascript-testing-patterns to write Jest tests
|
||||
```
|
||||
|
||||
```
|
||||
Use @python-testing-patterns to write pytest tests
|
||||
```
|
||||
|
||||
```
|
||||
Use @unit-testing-test-generate to generate unit tests
|
||||
```
|
||||
|
||||
### Phase 3: Integration Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-testing-observability-api-mock` - API testing
|
||||
- `e2e-testing-patterns` - Integration patterns
|
||||
|
||||
#### Actions
|
||||
1. Design integration tests
|
||||
2. Set up test databases
|
||||
3. Configure API mocks
|
||||
4. Test service interactions
|
||||
5. Verify data flows
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-testing-observability-api-mock to test APIs
|
||||
```
|
||||
|
||||
### Phase 4: E2E Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `playwright-skill` - Playwright testing
|
||||
- `e2e-testing-patterns` - E2E patterns
|
||||
- `webapp-testing` - Web app testing
|
||||
|
||||
#### Actions
|
||||
1. Design E2E scenarios
|
||||
2. Write test scripts
|
||||
3. Configure test data
|
||||
4. Set up parallel execution
|
||||
5. Implement visual regression
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @playwright-skill to create E2E tests
|
||||
```
|
||||
|
||||
```
|
||||
Use @e2e-testing-patterns to design E2E strategy
|
||||
```
|
||||
|
||||
### Phase 5: Browser Automation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `browser-automation` - Browser automation
|
||||
- `webapp-testing` - Browser testing
|
||||
- `screenshots` - Screenshot automation
|
||||
|
||||
#### Actions
|
||||
1. Set up browser automation
|
||||
2. Configure headless testing
|
||||
3. Implement visual testing
|
||||
4. Capture screenshots
|
||||
5. Test responsive design
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @browser-automation to automate browser tasks
|
||||
```
|
||||
|
||||
```
|
||||
Use @screenshots to capture marketing screenshots
|
||||
```
|
||||
|
||||
### Phase 6: Performance Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `performance-engineer` - Performance engineering
|
||||
- `performance-profiling` - Performance profiling
|
||||
- `web-performance-optimization` - Web performance
|
||||
|
||||
#### Actions
|
||||
1. Design performance tests
|
||||
2. Set up load testing
|
||||
3. Measure response times
|
||||
4. Identify bottlenecks
|
||||
5. Optimize performance
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @performance-engineer to test application performance
|
||||
```
|
||||
|
||||
### Phase 7: Code Review
|
||||
|
||||
#### Skills to Invoke
|
||||
- `code-reviewer` - AI code review
|
||||
- `code-review-excellence` - Review best practices
|
||||
- `find-bugs` - Bug detection
|
||||
- `security-scanning-security-sast` - Security scanning
|
||||
|
||||
#### Actions
|
||||
1. Configure review tools
|
||||
2. Run automated reviews
|
||||
3. Check for bugs
|
||||
4. Verify security
|
||||
5. Approve changes
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @code-reviewer to review pull requests
|
||||
```
|
||||
|
||||
```
|
||||
Use @find-bugs to detect bugs in code
|
||||
```
|
||||
|
||||
### Phase 8: Quality Gates
|
||||
|
||||
#### Skills to Invoke
|
||||
- `lint-and-validate` - Linting
|
||||
- `verification-before-completion` - Verification
|
||||
|
||||
#### Actions
|
||||
1. Configure linters
|
||||
2. Set up formatters
|
||||
3. Define quality metrics
|
||||
4. Implement gates
|
||||
5. Monitor compliance
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @lint-and-validate to check code quality
|
||||
```
|
||||
|
||||
```
|
||||
Use @verification-before-completion to verify changes
|
||||
```
|
||||
|
||||
## Testing Pyramid
|
||||
|
||||
```
|
||||
/ / \ E2E Tests (10%)
|
||||
/---- / \ Integration Tests (20%)
|
||||
/-------- / \ Unit Tests (70%)
|
||||
/------------```
|
||||
|
||||
## Quality Gates Checklist
|
||||
|
||||
- [ ] Unit test coverage > 80%
|
||||
- [ ] All tests passing
|
||||
- [ ] E2E tests for critical paths
|
||||
- [ ] Performance benchmarks met
|
||||
- [ ] Security scan passed
|
||||
- [ ] Code review approved
|
||||
- [ ] Linting clean
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - Development workflow
|
||||
- `security-audit` - Security testing
|
||||
- `cloud-devops` - CI/CD integration
|
||||
- `ai-ml` - AI testing
|
||||
184
skills/web-security-testing/SKILL.md
Normal file
184
skills/web-security-testing/SKILL.md
Normal file
@@ -0,0 +1,184 @@
|
||||
---
|
||||
name: web-security-testing
|
||||
description: "Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: security
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Web Security Testing Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for testing web applications against OWASP Top 10 vulnerabilities including injection attacks, XSS, broken authentication, and access control issues.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Testing web application security
|
||||
- Performing OWASP Top 10 assessment
|
||||
- Conducting penetration tests
|
||||
- Validating security controls
|
||||
- Bug bounty hunting
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Reconnaissance
|
||||
|
||||
#### Skills to Invoke
|
||||
- `scanning-tools` - Security scanning
|
||||
- `top-web-vulnerabilities` - OWASP knowledge
|
||||
|
||||
#### Actions
|
||||
1. Map application surface
|
||||
2. Identify technologies
|
||||
3. Discover endpoints
|
||||
4. Find subdomains
|
||||
5. Document findings
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @scanning-tools to perform web application reconnaissance
|
||||
```
|
||||
|
||||
### Phase 2: Injection Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `sql-injection-testing` - SQL injection
|
||||
- `sqlmap-database-pentesting` - SQLMap
|
||||
|
||||
#### Actions
|
||||
1. Test SQL injection
|
||||
2. Test NoSQL injection
|
||||
3. Test command injection
|
||||
4. Test LDAP injection
|
||||
5. Document vulnerabilities
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @sql-injection-testing to test for SQL injection
|
||||
```
|
||||
|
||||
```
|
||||
Use @sqlmap-database-pentesting to automate SQL injection testing
|
||||
```
|
||||
|
||||
### Phase 3: XSS Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `xss-html-injection` - XSS testing
|
||||
- `html-injection-testing` - HTML injection
|
||||
|
||||
#### Actions
|
||||
1. Test reflected XSS
|
||||
2. Test stored XSS
|
||||
3. Test DOM-based XSS
|
||||
4. Test XSS filters
|
||||
5. Document findings
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @xss-html-injection to test for cross-site scripting
|
||||
```
|
||||
|
||||
### Phase 4: Authentication Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `broken-authentication` - Authentication testing
|
||||
|
||||
#### Actions
|
||||
1. Test credential stuffing
|
||||
2. Test brute force protection
|
||||
3. Test session management
|
||||
4. Test password policies
|
||||
5. Test MFA implementation
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @broken-authentication to test authentication security
|
||||
```
|
||||
|
||||
### Phase 5: Access Control Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `idor-testing` - IDOR testing
|
||||
- `file-path-traversal` - Path traversal
|
||||
|
||||
#### Actions
|
||||
1. Test vertical privilege escalation
|
||||
2. Test horizontal privilege escalation
|
||||
3. Test IDOR vulnerabilities
|
||||
4. Test directory traversal
|
||||
5. Test unauthorized access
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @idor-testing to test for insecure direct object references
|
||||
```
|
||||
|
||||
```
|
||||
Use @file-path-traversal to test for path traversal
|
||||
```
|
||||
|
||||
### Phase 6: Security Headers
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-security-best-practices` - Security headers
|
||||
|
||||
#### Actions
|
||||
1. Check CSP implementation
|
||||
2. Verify HSTS configuration
|
||||
3. Test X-Frame-Options
|
||||
4. Check X-Content-Type-Options
|
||||
5. Verify referrer policy
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-security-best-practices to audit security headers
|
||||
```
|
||||
|
||||
### Phase 7: Reporting
|
||||
|
||||
#### Skills to Invoke
|
||||
- `reporting-standards` - Security reporting
|
||||
|
||||
#### Actions
|
||||
1. Document vulnerabilities
|
||||
2. Assess risk levels
|
||||
3. Provide remediation
|
||||
4. Create proof of concept
|
||||
5. Generate report
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @reporting-standards to create security report
|
||||
```
|
||||
|
||||
## OWASP Top 10 Checklist
|
||||
|
||||
- [ ] A01: Broken Access Control
|
||||
- [ ] A02: Cryptographic Failures
|
||||
- [ ] A03: Injection
|
||||
- [ ] A04: Insecure Design
|
||||
- [ ] A05: Security Misconfiguration
|
||||
- [ ] A06: Vulnerable Components
|
||||
- [ ] A07: Authentication Failures
|
||||
- [ ] A08: Software/Data Integrity
|
||||
- [ ] A09: Logging/Monitoring
|
||||
- [ ] A10: SSRF
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] All OWASP Top 10 tested
|
||||
- [ ] Vulnerabilities documented
|
||||
- [ ] Proof of concepts captured
|
||||
- [ ] Remediation provided
|
||||
- [ ] Report generated
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `security-audit` - Security auditing
|
||||
- `api-security-testing` - API security
|
||||
- `wordpress-security` - WordPress security
|
||||
204
skills/wordpress-plugin-development/SKILL.md
Normal file
204
skills/wordpress-plugin-development/SKILL.md
Normal file
@@ -0,0 +1,204 @@
|
||||
---
|
||||
name: wordpress-plugin-development
|
||||
description: "WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, and security best practices."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: wordpress-development
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# WordPress Plugin Development Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for creating WordPress plugins with proper architecture, hooks system, admin interfaces, REST API endpoints, and security practices.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Creating custom WordPress plugins
|
||||
- Extending WordPress functionality
|
||||
- Building admin interfaces
|
||||
- Adding REST API endpoints
|
||||
- Integrating third-party services
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Plugin Setup
|
||||
|
||||
#### Skills to Invoke
|
||||
- `app-builder` - Project scaffolding
|
||||
- `backend-dev-guidelines` - Backend patterns
|
||||
|
||||
#### Actions
|
||||
1. Create plugin directory structure
|
||||
2. Set up main plugin file with header
|
||||
3. Implement activation/deactivation hooks
|
||||
4. Set up autoloading
|
||||
5. Configure text domain
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @app-builder to scaffold a new WordPress plugin
|
||||
```
|
||||
|
||||
### Phase 2: Plugin Architecture
|
||||
|
||||
#### Skills to Invoke
|
||||
- `backend-dev-guidelines` - Architecture patterns
|
||||
|
||||
#### Actions
|
||||
1. Design plugin class structure
|
||||
2. Implement singleton pattern
|
||||
3. Create loader class
|
||||
4. Set up dependency injection
|
||||
5. Configure plugin lifecycle
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @backend-dev-guidelines to design plugin architecture
|
||||
```
|
||||
|
||||
### Phase 3: Hooks Implementation
|
||||
|
||||
#### Skills to Invoke
|
||||
- `wordpress-penetration-testing` - WordPress patterns
|
||||
|
||||
#### Actions
|
||||
1. Register action hooks
|
||||
2. Create filter hooks
|
||||
3. Implement callback functions
|
||||
4. Set up hook priorities
|
||||
5. Add conditional hooks
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @wordpress-penetration-testing to understand WordPress hooks
|
||||
```
|
||||
|
||||
### Phase 4: Admin Interface
|
||||
|
||||
#### Skills to Invoke
|
||||
- `frontend-developer` - Admin UI
|
||||
|
||||
#### Actions
|
||||
1. Create admin menu
|
||||
2. Build settings pages
|
||||
3. Implement options registration
|
||||
4. Add settings sections/fields
|
||||
5. Create admin notices
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @frontend-developer to create WordPress admin interface
|
||||
```
|
||||
|
||||
### Phase 5: Database Operations
|
||||
|
||||
#### Skills to Invoke
|
||||
- `database-design` - Database design
|
||||
- `postgresql` - Database patterns
|
||||
|
||||
#### Actions
|
||||
1. Create custom tables
|
||||
2. Implement CRUD operations
|
||||
3. Add data validation
|
||||
4. Set up data sanitization
|
||||
5. Create data upgrade routines
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @database-design to design plugin database schema
|
||||
```
|
||||
|
||||
### Phase 6: REST API
|
||||
|
||||
#### Skills to Invoke
|
||||
- `api-design-principles` - API design
|
||||
- `api-patterns` - API patterns
|
||||
|
||||
#### Actions
|
||||
1. Register REST routes
|
||||
2. Create endpoint callbacks
|
||||
3. Implement permission callbacks
|
||||
4. Add request validation
|
||||
5. Document API endpoints
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @api-design-principles to create WordPress REST API endpoints
|
||||
```
|
||||
|
||||
### Phase 7: Security
|
||||
|
||||
#### Skills to Invoke
|
||||
- `wordpress-penetration-testing` - WordPress security
|
||||
- `security-scanning-security-sast` - Security scanning
|
||||
|
||||
#### Actions
|
||||
1. Implement nonce verification
|
||||
2. Add capability checks
|
||||
3. Sanitize all inputs
|
||||
4. Escape all outputs
|
||||
5. Secure database queries
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @wordpress-penetration-testing to audit plugin security
|
||||
```
|
||||
|
||||
### Phase 8: Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `test-automator` - Test automation
|
||||
- `php-pro` - PHP testing
|
||||
|
||||
#### Actions
|
||||
1. Set up PHPUnit
|
||||
2. Create unit tests
|
||||
3. Write integration tests
|
||||
4. Test with WordPress test suite
|
||||
5. Configure CI
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @test-automator to set up plugin testing
|
||||
```
|
||||
|
||||
## Plugin Structure
|
||||
|
||||
```
|
||||
plugin-name/
|
||||
├── plugin-name.php
|
||||
├── includes/
|
||||
│ ├── class-plugin.php
|
||||
│ ├── class-loader.php
|
||||
│ ├── class-activator.php
|
||||
│ └── class-deactivator.php
|
||||
├── admin/
|
||||
│ ├── class-plugin-admin.php
|
||||
│ ├── css/
|
||||
│ └── js/
|
||||
├── public/
|
||||
│ ├── class-plugin-public.php
|
||||
│ ├── css/
|
||||
│ └── js/
|
||||
├── languages/
|
||||
└── vendor/
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Plugin activates without errors
|
||||
- [ ] All hooks working
|
||||
- [ ] Admin interface functional
|
||||
- [ ] Security measures implemented
|
||||
- [ ] Tests passing
|
||||
- [ ] Documentation complete
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `wordpress` - WordPress development
|
||||
- `wordpress-theme-development` - Theme development
|
||||
- `wordpress-woocommerce` - WooCommerce
|
||||
189
skills/wordpress-theme-development/SKILL.md
Normal file
189
skills/wordpress-theme-development/SKILL.md
Normal file
@@ -0,0 +1,189 @@
|
||||
---
|
||||
name: wordpress-theme-development
|
||||
description: "WordPress theme development workflow covering theme architecture, template hierarchy, custom post types, block editor support, and responsive design."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: wordpress-development
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# WordPress Theme Development Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for creating custom WordPress themes from scratch, including modern block editor (Gutenberg) support, template hierarchy, and responsive design.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Creating custom WordPress themes
|
||||
- Converting designs to WordPress themes
|
||||
- Adding block editor support
|
||||
- Implementing custom post types
|
||||
- Building child themes
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Theme Setup
|
||||
|
||||
#### Skills to Invoke
|
||||
- `app-builder` - Project scaffolding
|
||||
- `frontend-developer` - Frontend development
|
||||
|
||||
#### Actions
|
||||
1. Create theme directory structure
|
||||
2. Set up style.css with theme header
|
||||
3. Create functions.php
|
||||
4. Configure theme support
|
||||
5. Set up enqueue scripts/styles
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @app-builder to scaffold a new WordPress theme project
|
||||
```
|
||||
|
||||
### Phase 2: Template Hierarchy
|
||||
|
||||
#### Skills to Invoke
|
||||
- `frontend-developer` - Template development
|
||||
|
||||
#### Actions
|
||||
1. Create index.php (fallback template)
|
||||
2. Implement header.php and footer.php
|
||||
3. Create single.php for posts
|
||||
4. Create page.php for pages
|
||||
5. Add archive.php for archives
|
||||
6. Implement search.php and 404.php
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @frontend-developer to create WordPress template files
|
||||
```
|
||||
|
||||
### Phase 3: Theme Functions
|
||||
|
||||
#### Skills to Invoke
|
||||
- `backend-dev-guidelines` - Backend patterns
|
||||
|
||||
#### Actions
|
||||
1. Register navigation menus
|
||||
2. Add theme support (thumbnails, RSS, etc.)
|
||||
3. Register widget areas
|
||||
4. Create custom template tags
|
||||
5. Implement helper functions
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @backend-dev-guidelines to create theme functions
|
||||
```
|
||||
|
||||
### Phase 4: Custom Post Types
|
||||
|
||||
#### Skills to Invoke
|
||||
- `wordpress-penetration-testing` - WordPress patterns
|
||||
|
||||
#### Actions
|
||||
1. Register custom post types
|
||||
2. Create custom taxonomies
|
||||
3. Add custom meta boxes
|
||||
4. Implement custom fields
|
||||
5. Create archive templates
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @wordpress-penetration-testing to understand WordPress CPT patterns
|
||||
```
|
||||
|
||||
### Phase 5: Block Editor Support
|
||||
|
||||
#### Skills to Invoke
|
||||
- `frontend-developer` - Block development
|
||||
|
||||
#### Actions
|
||||
1. Enable block editor support
|
||||
2. Register custom blocks
|
||||
3. Create block styles
|
||||
4. Add block patterns
|
||||
5. Configure block templates
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @frontend-developer to create custom Gutenberg blocks
|
||||
```
|
||||
|
||||
### Phase 6: Styling and Design
|
||||
|
||||
#### Skills to Invoke
|
||||
- `frontend-design` - UI design
|
||||
- `tailwind-patterns` - Tailwind CSS
|
||||
|
||||
#### Actions
|
||||
1. Implement responsive design
|
||||
2. Add CSS framework or custom styles
|
||||
3. Create design system
|
||||
4. Implement theme customizer
|
||||
5. Add accessibility features
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @frontend-design to create responsive theme design
|
||||
```
|
||||
|
||||
### Phase 7: Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `playwright-skill` - Browser testing
|
||||
- `webapp-testing` - Web app testing
|
||||
|
||||
#### Actions
|
||||
1. Test across browsers
|
||||
2. Verify responsive breakpoints
|
||||
3. Test block editor
|
||||
4. Check accessibility
|
||||
5. Performance testing
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @playwright-skill to test WordPress theme
|
||||
```
|
||||
|
||||
## Theme Structure
|
||||
|
||||
```
|
||||
theme-name/
|
||||
├── style.css
|
||||
├── functions.php
|
||||
├── index.php
|
||||
├── header.php
|
||||
├── footer.php
|
||||
├── sidebar.php
|
||||
├── single.php
|
||||
├── page.php
|
||||
├── archive.php
|
||||
├── search.php
|
||||
├── 404.php
|
||||
├── comments.php
|
||||
├── template-parts/
|
||||
├── inc/
|
||||
├── assets/
|
||||
│ ├── css/
|
||||
│ ├── js/
|
||||
│ └── images/
|
||||
└── languages/
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] All templates working
|
||||
- [ ] Block editor supported
|
||||
- [ ] Responsive design verified
|
||||
- [ ] Accessibility checked
|
||||
- [ ] Performance optimized
|
||||
- [ ] Cross-browser tested
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `wordpress` - WordPress development
|
||||
- `wordpress-plugin-development` - Plugin development
|
||||
- `wordpress-woocommerce` - WooCommerce
|
||||
188
skills/wordpress-woocommerce-development/SKILL.md
Normal file
188
skills/wordpress-woocommerce-development/SKILL.md
Normal file
@@ -0,0 +1,188 @@
|
||||
---
|
||||
name: wordpress-woocommerce-development
|
||||
description: "WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: wordpress-development
|
||||
category: granular-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# WordPress WooCommerce Development Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Specialized workflow for building WooCommerce stores including setup, payment gateway integration, shipping configuration, custom product types, and store optimization.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Setting up WooCommerce stores
|
||||
- Integrating payment gateways
|
||||
- Configuring shipping methods
|
||||
- Creating custom product types
|
||||
- Building subscription products
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Store Setup
|
||||
|
||||
#### Skills to Invoke
|
||||
- `app-builder` - Project scaffolding
|
||||
- `wordpress-penetration-testing` - WordPress patterns
|
||||
|
||||
#### Actions
|
||||
1. Install WooCommerce
|
||||
2. Run setup wizard
|
||||
3. Configure store settings
|
||||
4. Set up tax rules
|
||||
5. Configure currency
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @app-builder to set up WooCommerce store
|
||||
```
|
||||
|
||||
### Phase 2: Product Configuration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `wordpress-penetration-testing` - WooCommerce patterns
|
||||
|
||||
#### Actions
|
||||
1. Create product categories
|
||||
2. Add product attributes
|
||||
3. Configure product types
|
||||
4. Set up variable products
|
||||
5. Add product images
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @wordpress-penetration-testing to configure WooCommerce products
|
||||
```
|
||||
|
||||
### Phase 3: Payment Integration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `payment-integration` - Payment processing
|
||||
- `stripe-integration` - Stripe
|
||||
- `paypal-integration` - PayPal
|
||||
|
||||
#### Actions
|
||||
1. Choose payment gateways
|
||||
2. Configure Stripe
|
||||
3. Set up PayPal
|
||||
4. Add offline payments
|
||||
5. Test payment flows
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @stripe-integration to integrate Stripe payments
|
||||
```
|
||||
|
||||
```
|
||||
Use @paypal-integration to integrate PayPal
|
||||
```
|
||||
|
||||
### Phase 4: Shipping Configuration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `wordpress-penetration-testing` - WooCommerce shipping
|
||||
|
||||
#### Actions
|
||||
1. Set up shipping zones
|
||||
2. Configure shipping methods
|
||||
3. Add flat rate shipping
|
||||
4. Set up free shipping
|
||||
5. Integrate carriers
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @wordpress-penetration-testing to configure shipping
|
||||
```
|
||||
|
||||
### Phase 5: Store Customization
|
||||
|
||||
#### Skills to Invoke
|
||||
- `frontend-developer` - Store customization
|
||||
- `frontend-design` - Store design
|
||||
|
||||
#### Actions
|
||||
1. Customize product pages
|
||||
2. Modify cart page
|
||||
3. Style checkout flow
|
||||
4. Create custom templates
|
||||
5. Add custom fields
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @frontend-developer to customize WooCommerce templates
|
||||
```
|
||||
|
||||
### Phase 6: Extensions
|
||||
|
||||
#### Skills to Invoke
|
||||
- `wordpress-penetration-testing` - WooCommerce extensions
|
||||
|
||||
#### Actions
|
||||
1. Install required extensions
|
||||
2. Configure subscriptions
|
||||
3. Set up bookings
|
||||
4. Add memberships
|
||||
5. Integrate marketplace
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @wordpress-penetration-testing to configure WooCommerce extensions
|
||||
```
|
||||
|
||||
### Phase 7: Optimization
|
||||
|
||||
#### Skills to Invoke
|
||||
- `web-performance-optimization` - Performance
|
||||
- `database-optimizer` - Database optimization
|
||||
|
||||
#### Actions
|
||||
1. Optimize product images
|
||||
2. Enable caching
|
||||
3. Optimize database
|
||||
4. Configure CDN
|
||||
5. Set up lazy loading
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @web-performance-optimization to optimize WooCommerce store
|
||||
```
|
||||
|
||||
### Phase 8: Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `playwright-skill` - E2E testing
|
||||
- `test-automator` - Test automation
|
||||
|
||||
#### Actions
|
||||
1. Test checkout flow
|
||||
2. Verify payment processing
|
||||
3. Test email notifications
|
||||
4. Check mobile experience
|
||||
5. Performance testing
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @playwright-skill to test WooCommerce checkout flow
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
- [ ] Products displaying correctly
|
||||
- [ ] Checkout flow working
|
||||
- [ ] Payments processing
|
||||
- [ ] Shipping calculating
|
||||
- [ ] Emails sending
|
||||
- [ ] Mobile responsive
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `wordpress` - WordPress development
|
||||
- `wordpress-theme-development` - Theme development
|
||||
- `wordpress-plugin-development` - Plugin development
|
||||
- `payment-integration` - Payment processing
|
||||
319
skills/wordpress/SKILL.md
Normal file
319
skills/wordpress/SKILL.md
Normal file
@@ -0,0 +1,319 @@
|
||||
---
|
||||
name: wordpress
|
||||
description: "Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening."
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: software-development
|
||||
category: workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# WordPress Development Workflow Bundle
|
||||
|
||||
## Overview
|
||||
|
||||
Comprehensive WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security. This bundle orchestrates skills for building production-ready WordPress sites and applications.
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use this workflow when:
|
||||
- Building new WordPress websites
|
||||
- Creating custom themes
|
||||
- Developing WordPress plugins
|
||||
- Setting up WooCommerce stores
|
||||
- Optimizing WordPress performance
|
||||
- Hardening WordPress security
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: WordPress Setup
|
||||
|
||||
#### Skills to Invoke
|
||||
- `app-builder` - Project scaffolding
|
||||
- `environment-setup-guide` - Development environment
|
||||
|
||||
#### Actions
|
||||
1. Set up local development environment (LocalWP, Docker, or Valet)
|
||||
2. Install WordPress
|
||||
3. Configure development database
|
||||
4. Set up version control
|
||||
5. Configure wp-config.php for development
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @app-builder to scaffold a new WordPress project with modern tooling
|
||||
```
|
||||
|
||||
### Phase 2: Theme Development
|
||||
|
||||
#### Skills to Invoke
|
||||
- `frontend-developer` - Component development
|
||||
- `frontend-design` - UI implementation
|
||||
- `tailwind-patterns` - Styling
|
||||
- `web-performance-optimization` - Performance
|
||||
|
||||
#### Actions
|
||||
1. Design theme architecture
|
||||
2. Create theme files (style.css, functions.php, index.php)
|
||||
3. Implement template hierarchy
|
||||
4. Create custom page templates
|
||||
5. Add custom post types and taxonomies
|
||||
6. Implement theme customization options
|
||||
7. Add responsive design
|
||||
|
||||
#### Theme Structure
|
||||
```
|
||||
theme-name/
|
||||
├── style.css
|
||||
├── functions.php
|
||||
├── index.php
|
||||
├── header.php
|
||||
├── footer.php
|
||||
├── sidebar.php
|
||||
├── single.php
|
||||
├── page.php
|
||||
├── archive.php
|
||||
├── search.php
|
||||
├── 404.php
|
||||
├── template-parts/
|
||||
├── inc/
|
||||
├── assets/
|
||||
│ ├── css/
|
||||
│ ├── js/
|
||||
│ └── images/
|
||||
└── languages/
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @frontend-developer to create a custom WordPress theme with React components
|
||||
```
|
||||
|
||||
```
|
||||
Use @tailwind-patterns to style WordPress theme with modern CSS
|
||||
```
|
||||
|
||||
### Phase 3: Plugin Development
|
||||
|
||||
#### Skills to Invoke
|
||||
- `backend-dev-guidelines` - Backend standards
|
||||
- `api-design-principles` - API design
|
||||
- `auth-implementation-patterns` - Authentication
|
||||
|
||||
#### Actions
|
||||
1. Design plugin architecture
|
||||
2. Create plugin boilerplate
|
||||
3. Implement hooks (actions and filters)
|
||||
4. Create admin interfaces
|
||||
5. Add custom database tables
|
||||
6. Implement REST API endpoints
|
||||
7. Add settings and options pages
|
||||
|
||||
#### Plugin Structure
|
||||
```
|
||||
plugin-name/
|
||||
├── plugin-name.php
|
||||
├── includes/
|
||||
│ ├── class-plugin-activator.php
|
||||
│ ├── class-plugin-deactivator.php
|
||||
│ ├── class-plugin-loader.php
|
||||
│ └── class-plugin.php
|
||||
├── admin/
|
||||
│ ├── class-plugin-admin.php
|
||||
│ ├── css/
|
||||
│ └── js/
|
||||
├── public/
|
||||
│ ├── class-plugin-public.php
|
||||
│ ├── css/
|
||||
│ └── js/
|
||||
└── languages/
|
||||
```
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @backend-dev-guidelines to create a WordPress plugin with proper architecture
|
||||
```
|
||||
|
||||
### Phase 4: WooCommerce Integration
|
||||
|
||||
#### Skills to Invoke
|
||||
- `payment-integration` - Payment processing
|
||||
- `stripe-integration` - Stripe payments
|
||||
- `billing-automation` - Billing workflows
|
||||
|
||||
#### Actions
|
||||
1. Install and configure WooCommerce
|
||||
2. Create custom product types
|
||||
3. Customize checkout flow
|
||||
4. Integrate payment gateways
|
||||
5. Set up shipping methods
|
||||
6. Create custom order statuses
|
||||
7. Implement subscription products
|
||||
8. Add custom email templates
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @payment-integration to set up WooCommerce with Stripe
|
||||
```
|
||||
|
||||
```
|
||||
Use @billing-automation to create subscription products in WooCommerce
|
||||
```
|
||||
|
||||
### Phase 5: Performance Optimization
|
||||
|
||||
#### Skills to Invoke
|
||||
- `web-performance-optimization` - Performance optimization
|
||||
- `database-optimizer` - Database optimization
|
||||
|
||||
#### Actions
|
||||
1. Implement caching (object, page, browser)
|
||||
2. Optimize images (lazy loading, WebP)
|
||||
3. Minify and combine assets
|
||||
4. Enable CDN
|
||||
5. Optimize database queries
|
||||
6. Implement lazy loading
|
||||
7. Configure OPcache
|
||||
8. Set up Redis/Memcached
|
||||
|
||||
#### Performance Checklist
|
||||
- [ ] Page load time < 3 seconds
|
||||
- [ ] Time to First Byte < 200ms
|
||||
- [ ] Largest Contentful Paint < 2.5s
|
||||
- [ ] Cumulative Layout Shift < 0.1
|
||||
- [ ] First Input Delay < 100ms
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @web-performance-optimization to audit and improve WordPress performance
|
||||
```
|
||||
|
||||
### Phase 6: Security Hardening
|
||||
|
||||
#### Skills to Invoke
|
||||
- `security-auditor` - Security audit
|
||||
- `wordpress-penetration-testing` - WordPress security testing
|
||||
- `sast-configuration` - Static analysis
|
||||
|
||||
#### Actions
|
||||
1. Update WordPress core, themes, plugins
|
||||
2. Implement security headers
|
||||
3. Configure file permissions
|
||||
4. Set up firewall rules
|
||||
5. Enable two-factor authentication
|
||||
6. Implement rate limiting
|
||||
7. Configure security logging
|
||||
8. Set up malware scanning
|
||||
|
||||
#### Security Checklist
|
||||
- [ ] WordPress core updated
|
||||
- [ ] All plugins/themes updated
|
||||
- [ ] Strong passwords enforced
|
||||
- [ ] Two-factor authentication enabled
|
||||
- [ ] Security headers configured
|
||||
- [ ] XML-RPC disabled or protected
|
||||
- [ ] File editing disabled
|
||||
- [ ] Database prefix changed
|
||||
- [ ] Regular backups configured
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @wordpress-penetration-testing to audit WordPress security
|
||||
```
|
||||
|
||||
```
|
||||
Use @security-auditor to perform comprehensive security review
|
||||
```
|
||||
|
||||
### Phase 7: Testing
|
||||
|
||||
#### Skills to Invoke
|
||||
- `test-automator` - Test automation
|
||||
- `playwright-skill` - E2E testing
|
||||
- `webapp-testing` - Web app testing
|
||||
|
||||
#### Actions
|
||||
1. Write unit tests for custom code
|
||||
2. Create integration tests
|
||||
3. Set up E2E tests
|
||||
4. Test cross-browser compatibility
|
||||
5. Test responsive design
|
||||
6. Performance testing
|
||||
7. Security testing
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @playwright-skill to create E2E tests for WordPress site
|
||||
```
|
||||
|
||||
### Phase 8: Deployment
|
||||
|
||||
#### Skills to Invoke
|
||||
- `deployment-engineer` - Deployment
|
||||
- `cicd-automation-workflow-automate` - CI/CD
|
||||
- `github-actions-templates` - GitHub Actions
|
||||
|
||||
#### Actions
|
||||
1. Set up staging environment
|
||||
2. Configure deployment pipeline
|
||||
3. Set up database migrations
|
||||
4. Configure environment variables
|
||||
5. Enable maintenance mode during deployment
|
||||
6. Deploy to production
|
||||
7. Verify deployment
|
||||
8. Monitor post-deployment
|
||||
|
||||
#### Copy-Paste Prompts
|
||||
```
|
||||
Use @deployment-engineer to set up WordPress deployment pipeline
|
||||
```
|
||||
|
||||
## WordPress-Specific Workflows
|
||||
|
||||
### Custom Post Type Development
|
||||
```php
|
||||
register_post_type('book', [
|
||||
'labels' => [...],
|
||||
'public' => true,
|
||||
'has_archive' => true,
|
||||
'supports' => ['title', 'editor', 'thumbnail', 'excerpt'],
|
||||
'menu_icon' => 'dashicons-book',
|
||||
]);
|
||||
```
|
||||
|
||||
### Custom REST API Endpoint
|
||||
```php
|
||||
add_action('rest_api_init', function() {
|
||||
register_rest_route('myplugin/v1', '/books', [
|
||||
'methods' => 'GET',
|
||||
'callback' => 'get_books',
|
||||
'permission_callback' => '__return_true',
|
||||
]);
|
||||
});
|
||||
```
|
||||
|
||||
### WooCommerce Custom Product Type
|
||||
```php
|
||||
add_action('init', function() {
|
||||
class WC_Product_Custom extends WC_Product {
|
||||
// Custom product implementation
|
||||
}
|
||||
});
|
||||
```
|
||||
|
||||
## Quality Gates
|
||||
|
||||
Before moving to next phase, verify:
|
||||
- [ ] All custom code tested
|
||||
- [ ] Security scan passed
|
||||
- [ ] Performance targets met
|
||||
- [ ] Cross-browser tested
|
||||
- [ ] Mobile responsive verified
|
||||
- [ ] Accessibility checked (WCAG 2.1)
|
||||
|
||||
## Related Workflow Bundles
|
||||
|
||||
- `development` - General web development
|
||||
- `security-audit` - Security testing
|
||||
- `testing-qa` - Testing workflow
|
||||
- `ecommerce` - E-commerce development
|
||||
185
skills/workflow- bundlesREADME.md
Normal file
185
skills/workflow- bundlesREADME.md
Normal file
@@ -0,0 +1,185 @@
|
||||
# Workflow Bundles
|
||||
|
||||
Consolidated and granular workflow bundles that orchestrate multiple skills for specific development and operational scenarios.
|
||||
|
||||
## Granular Workflow Bundles (Specialized)
|
||||
|
||||
### Frontend Development
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `react-nextjs-development` | React and Next.js 14+ with App Router, Server Components, TypeScript, Tailwind | nextjs-app-router-patterns, react-patterns, tailwind-patterns |
|
||||
|
||||
### Backend Development
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `python-fastapi-development` | FastAPI backend with async patterns, SQLAlchemy, Pydantic, auth | fastapi-pro, fastapi-router-py, pydantic-models-py |
|
||||
|
||||
### WordPress Development
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `wordpress-theme-development` | Custom WordPress themes, block editor, template hierarchy | frontend-developer, wordpress-penetration-testing |
|
||||
| `wordpress-plugin-development` | WordPress plugins, hooks, admin interfaces, REST API | backend-dev-guidelines, wordpress-penetration-testing |
|
||||
| `wordpress-woocommerce-development` | WooCommerce stores, payments, shipping, customization | payment-integration, stripe-integration, paypal-integration |
|
||||
|
||||
### System Administration
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `bash-scripting` | Production bash scripts with defensive patterns, testing | bash-pro, bash-defensive-patterns, bats-testing-patterns |
|
||||
| `linux-troubleshooting` | Linux system diagnostics, performance, service issues | bash-linux, devops-troubleshooter, server-management |
|
||||
|
||||
### Security Testing
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `web-security-testing` | OWASP Top 10 testing, injection, XSS, authentication | sql-injection-testing, xss-html-injection, broken-authentication |
|
||||
| `api-security-testing` | REST/GraphQL API security, auth, rate limiting, fuzzing | api-fuzzing-bug-bounty, api-security-best-practices |
|
||||
|
||||
### AI/ML
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `rag-implementation` | RAG systems, embeddings, vector DB, chunking, retrieval | rag-engineer, embedding-strategies, vector-database-engineer |
|
||||
| `ai-agent-development` | Autonomous agents, multi-agent systems, CrewAI, LangGraph | ai-agents-architect, crewai, langgraph, autonomous-agents |
|
||||
|
||||
### Cloud/DevOps
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `kubernetes-deployment` | K8s deployment, Helm charts, service mesh, security | kubernetes-architect, helm-chart-scaffolding, istio-traffic-management |
|
||||
| `terraform-infrastructure` | Terraform IaC, modules, state management, CI/CD | terraform-skill, terraform-specialist, terraform-module-library |
|
||||
|
||||
### Database
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `postgresql-optimization` | PostgreSQL query tuning, indexing, configuration, monitoring | postgres-best-practices, sql-optimization-patterns, database-optimizer |
|
||||
|
||||
### Testing/QA
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `e2e-testing` | Playwright E2E, visual regression, cross-browser, CI/CD | playwright-skill, e2e-testing-patterns, browser-automation |
|
||||
|
||||
### Documentation
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `api-documentation` | OpenAPI specs, developer guides, code examples, interactive docs | api-documenter, openapi-spec-generation, api-documentation-generator |
|
||||
|
||||
## Consolidated Workflow Bundles
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `development` | Full-stack web and mobile development | app-builder, senior-fullstack, frontend-developer, backend-architect |
|
||||
| `wordpress` | WordPress theme, plugin, WooCommerce, security, performance | wordpress-penetration-testing, frontend-developer, payment-integration |
|
||||
| `os-scripting` | Shell scripting and system administration | bash-pro, bash-defensive-patterns, shellcheck-configuration |
|
||||
| `security-audit` | Security testing and penetration testing | vulnerability-scanner, sql-injection-testing, pentest-commands |
|
||||
| `ai-ml` | LLM applications, RAG, and AI agents | ai-agents-architect, rag-engineer, crewai, langgraph |
|
||||
| `cloud-devops` | Cloud infrastructure and DevOps | cloud-architect, kubernetes-architect, terraform-skill |
|
||||
| `database` | Database design and operations | database-architect, prisma-expert, data-engineer |
|
||||
| `testing-qa` | Testing and quality assurance | test-automator, playwright-skill, code-reviewer |
|
||||
| `documentation` | Documentation generation | docs-architect, c4-architecture, wiki-architect |
|
||||
| `office-productivity` | Document and office automation | libreoffice-writer, libreoffice-calc, libreoffice-impress |
|
||||
|
||||
## LibreOffice Skills
|
||||
|
||||
The following LibreOffice skills are available in the `skills/libreoffice/` directory:
|
||||
|
||||
| Skill | Description |
|
||||
|-------|-------------|
|
||||
| `writer` | Document creation and automation (ODT) |
|
||||
| `calc` | Spreadsheet automation (ODS) |
|
||||
| `impress` | Presentation creation (ODP) |
|
||||
| `draw` | Vector graphics and diagrams (ODG) |
|
||||
| `base` | Database management (ODB) |
|
||||
|
||||
## Usage
|
||||
|
||||
Each workflow bundle provides:
|
||||
|
||||
1. **When to Use** - Scenarios for invoking the workflow
|
||||
2. **Workflow Phases** - Step-by-step phases with skills to invoke
|
||||
3. **Copy-Paste Prompts** - Ready-to-use prompts for each phase
|
||||
4. **Quality Gates** - Checkpoints to verify before proceeding
|
||||
5. **Related Bundles** - Links to complementary workflows
|
||||
|
||||
### Example Usage
|
||||
|
||||
```
|
||||
Use @react-nextjs-development to build a new Next.js 14 application
|
||||
```
|
||||
|
||||
```
|
||||
Use @python-fastapi-development to create a REST API with FastAPI
|
||||
```
|
||||
|
||||
```
|
||||
Use @wordpress-theme-development to create a custom WordPress theme
|
||||
```
|
||||
|
||||
```
|
||||
Use @rag-implementation to build a RAG system with vector search
|
||||
```
|
||||
|
||||
```
|
||||
Use @kubernetes-deployment to deploy application to Kubernetes
|
||||
```
|
||||
|
||||
```
|
||||
Use @web-security-testing to perform OWASP Top 10 assessment
|
||||
```
|
||||
|
||||
```
|
||||
Use @libreoffice-writer to convert DOCX documents to ODT format
|
||||
```
|
||||
|
||||
## Structure
|
||||
|
||||
Each workflow bundle follows this structure:
|
||||
|
||||
```yaml
|
||||
---
|
||||
name: bundle-name
|
||||
description: "Brief description"
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: domain-category
|
||||
category: granular-workflow-bundle # or consolidated-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Bundle Name
|
||||
|
||||
## Overview
|
||||
...
|
||||
|
||||
## When to Use This Workflow
|
||||
...
|
||||
|
||||
## Workflow Phases
|
||||
...
|
||||
|
||||
## Quality Gates
|
||||
...
|
||||
|
||||
## Related Workflow Bundles
|
||||
...
|
||||
```
|
||||
|
||||
## Contributing
|
||||
|
||||
When creating new workflow bundles:
|
||||
|
||||
1. Identify common skill combinations
|
||||
2. Document clear workflow phases
|
||||
3. Provide copy-paste prompts
|
||||
4. Define quality gates
|
||||
5. Link related bundles
|
||||
|
||||
## License
|
||||
|
||||
Same as the parent project.
|
||||
185
skills/workflow_bundles_readme.md
Normal file
185
skills/workflow_bundles_readme.md
Normal file
@@ -0,0 +1,185 @@
|
||||
# Workflow Bundles
|
||||
|
||||
Consolidated and granular workflow bundles that orchestrate multiple skills for specific development and operational scenarios.
|
||||
|
||||
## Granular Workflow Bundles (Specialized)
|
||||
|
||||
### Frontend Development
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `react-nextjs-development` | React and Next.js 14+ with App Router, Server Components, TypeScript, Tailwind | nextjs-app-router-patterns, react-patterns, tailwind-patterns |
|
||||
|
||||
### Backend Development
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `python-fastapi-development` | FastAPI backend with async patterns, SQLAlchemy, Pydantic, auth | fastapi-pro, fastapi-router-py, pydantic-models-py |
|
||||
|
||||
### WordPress Development
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `wordpress-theme-development` | Custom WordPress themes, block editor, template hierarchy | frontend-developer, wordpress-penetration-testing |
|
||||
| `wordpress-plugin-development` | WordPress plugins, hooks, admin interfaces, REST API | backend-dev-guidelines, wordpress-penetration-testing |
|
||||
| `wordpress-woocommerce-development` | WooCommerce stores, payments, shipping, customization | payment-integration, stripe-integration, paypal-integration |
|
||||
|
||||
### System Administration
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `bash-scripting` | Production bash scripts with defensive patterns, testing | bash-pro, bash-defensive-patterns, bats-testing-patterns |
|
||||
| `linux-troubleshooting` | Linux system diagnostics, performance, service issues | bash-linux, devops-troubleshooter, server-management |
|
||||
|
||||
### Security Testing
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `web-security-testing` | OWASP Top 10 testing, injection, XSS, authentication | sql-injection-testing, xss-html-injection, broken-authentication |
|
||||
| `api-security-testing` | REST/GraphQL API security, auth, rate limiting, fuzzing | api-fuzzing-bug-bounty, api-security-best-practices |
|
||||
|
||||
### AI/ML
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `rag-implementation` | RAG systems, embeddings, vector DB, chunking, retrieval | rag-engineer, embedding-strategies, vector-database-engineer |
|
||||
| `ai-agent-development` | Autonomous agents, multi-agent systems, CrewAI, LangGraph | ai-agents-architect, crewai, langgraph, autonomous-agents |
|
||||
|
||||
### Cloud/DevOps
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `kubernetes-deployment` | K8s deployment, Helm charts, service mesh, security | kubernetes-architect, helm-chart-scaffolding, istio-traffic-management |
|
||||
| `terraform-infrastructure` | Terraform IaC, modules, state management, CI/CD | terraform-skill, terraform-specialist, terraform-module-library |
|
||||
|
||||
### Database
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `postgresql-optimization` | PostgreSQL query tuning, indexing, configuration, monitoring | postgres-best-practices, sql-optimization-patterns, database-optimizer |
|
||||
|
||||
### Testing/QA
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `e2e-testing` | Playwright E2E, visual regression, cross-browser, CI/CD | playwright-skill, e2e-testing-patterns, browser-automation |
|
||||
|
||||
### Documentation
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `api-documentation` | OpenAPI specs, developer guides, code examples, interactive docs | api-documenter, openapi-spec-generation, api-documentation-generator |
|
||||
|
||||
## Consolidated Workflow Bundles
|
||||
|
||||
| Bundle | Description | Key Skills |
|
||||
|--------|-------------|------------|
|
||||
| `development` | Full-stack web and mobile development | app-builder, senior-fullstack, frontend-developer, backend-architect |
|
||||
| `wordpress` | WordPress theme, plugin, WooCommerce, security, performance | wordpress-penetration-testing, frontend-developer, payment-integration |
|
||||
| `os-scripting` | Shell scripting and system administration | bash-pro, bash-defensive-patterns, shellcheck-configuration |
|
||||
| `security-audit` | Security testing and penetration testing | vulnerability-scanner, sql-injection-testing, pentest-commands |
|
||||
| `ai-ml` | LLM applications, RAG, and AI agents | ai-agents-architect, rag-engineer, crewai, langgraph |
|
||||
| `cloud-devops` | Cloud infrastructure and DevOps | cloud-architect, kubernetes-architect, terraform-skill |
|
||||
| `database` | Database design and operations | database-architect, prisma-expert, data-engineer |
|
||||
| `testing-qa` | Testing and quality assurance | test-automator, playwright-skill, code-reviewer |
|
||||
| `documentation` | Documentation generation | docs-architect, c4-architecture, wiki-architect |
|
||||
| `office-productivity` | Document and office automation | libreoffice-writer, libreoffice-calc, libreoffice-impress |
|
||||
|
||||
## LibreOffice Skills
|
||||
|
||||
The following LibreOffice skills are available in the `skills/libreoffice/` directory:
|
||||
|
||||
| Skill | Description |
|
||||
|-------|-------------|
|
||||
| `writer` | Document creation and automation (ODT) |
|
||||
| `calc` | Spreadsheet automation (ODS) |
|
||||
| `impress` | Presentation creation (ODP) |
|
||||
| `draw` | Vector graphics and diagrams (ODG) |
|
||||
| `base` | Database management (ODB) |
|
||||
|
||||
## Usage
|
||||
|
||||
Each workflow bundle provides:
|
||||
|
||||
1. **When to Use** - Scenarios for invoking the workflow
|
||||
2. **Workflow Phases** - Step-by-step phases with skills to invoke
|
||||
3. **Copy-Paste Prompts** - Ready-to-use prompts for each phase
|
||||
4. **Quality Gates** - Checkpoints to verify before proceeding
|
||||
5. **Related Bundles** - Links to complementary workflows
|
||||
|
||||
### Example Usage
|
||||
|
||||
```
|
||||
Use @react-nextjs-development to build a new Next.js 14 application
|
||||
```
|
||||
|
||||
```
|
||||
Use @python-fastapi-development to create a REST API with FastAPI
|
||||
```
|
||||
|
||||
```
|
||||
Use @wordpress-theme-development to create a custom WordPress theme
|
||||
```
|
||||
|
||||
```
|
||||
Use @rag-implementation to build a RAG system with vector search
|
||||
```
|
||||
|
||||
```
|
||||
Use @kubernetes-deployment to deploy application to Kubernetes
|
||||
```
|
||||
|
||||
```
|
||||
Use @web-security-testing to perform OWASP Top 10 assessment
|
||||
```
|
||||
|
||||
```
|
||||
Use @libreoffice-writer to convert DOCX documents to ODT format
|
||||
```
|
||||
|
||||
## Structure
|
||||
|
||||
Each workflow bundle follows this structure:
|
||||
|
||||
```yaml
|
||||
---
|
||||
name: bundle-name
|
||||
description: "Brief description"
|
||||
source: personal
|
||||
risk: safe
|
||||
domain: domain-category
|
||||
category: granular-workflow-bundle # or consolidated-workflow-bundle
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Bundle Name
|
||||
|
||||
## Overview
|
||||
...
|
||||
|
||||
## When to Use This Workflow
|
||||
...
|
||||
|
||||
## Workflow Phases
|
||||
...
|
||||
|
||||
## Quality Gates
|
||||
...
|
||||
|
||||
## Related Workflow Bundles
|
||||
...
|
||||
```
|
||||
|
||||
## Contributing
|
||||
|
||||
When creating new workflow bundles:
|
||||
|
||||
1. Identify common skill combinations
|
||||
2. Document clear workflow phases
|
||||
3. Provide copy-paste prompts
|
||||
4. Define quality gates
|
||||
5. Link related bundles
|
||||
|
||||
## License
|
||||
|
||||
Same as the parent project.
|
||||
@@ -161,6 +161,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "unknown"
|
||||
},
|
||||
{
|
||||
"id": "ai-agent-development",
|
||||
"path": "skills/ai-agent-development",
|
||||
"category": "uncategorized",
|
||||
"name": "ai-agent-development",
|
||||
"description": "AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "ai-agents-architect",
|
||||
"path": "skills/ai-agents-architect",
|
||||
@@ -170,6 +179,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "vibeship-spawner-skills (Apache 2.0)"
|
||||
},
|
||||
{
|
||||
"id": "ai-ml",
|
||||
"path": "skills/ai-ml",
|
||||
"category": "uncategorized",
|
||||
"name": "ai-ml",
|
||||
"description": "AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "ai-product",
|
||||
"path": "skills/ai-product",
|
||||
@@ -242,6 +260,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "unknown"
|
||||
},
|
||||
{
|
||||
"id": "android-jetpack-compose-expert",
|
||||
"path": "skills/android-jetpack-compose-expert",
|
||||
"category": "uncategorized",
|
||||
"name": "android-jetpack-compose-expert",
|
||||
"description": "Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.",
|
||||
"risk": "safe",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "angular",
|
||||
"path": "skills/angular",
|
||||
@@ -323,6 +350,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "api-documentation",
|
||||
"path": "skills/api-documentation",
|
||||
"category": "uncategorized",
|
||||
"name": "api-documentation",
|
||||
"description": "API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "api-documentation-generator",
|
||||
"path": "skills/api-documentation-generator",
|
||||
@@ -359,6 +395,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "api-security-testing",
|
||||
"path": "skills/api-security-testing",
|
||||
"category": "uncategorized",
|
||||
"name": "api-security-testing",
|
||||
"description": "API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "api-testing-observability-api-mock",
|
||||
"path": "skills/api-testing-observability-api-mock",
|
||||
@@ -1727,6 +1772,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "base",
|
||||
"path": "skills/libreoffice/base",
|
||||
"category": "libreoffice",
|
||||
"name": "base",
|
||||
"description": "Database management, forms, reports, and data operations with LibreOffice Base.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "basecamp-automation",
|
||||
"path": "skills/basecamp-automation",
|
||||
@@ -1763,6 +1817,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "bash-scripting",
|
||||
"path": "skills/bash-scripting",
|
||||
"category": "uncategorized",
|
||||
"name": "bash-scripting",
|
||||
"description": "Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "bats-testing-patterns",
|
||||
"path": "skills/bats-testing-patterns",
|
||||
@@ -1799,6 +1862,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "bevy-ecs-expert",
|
||||
"path": "skills/bevy-ecs-expert",
|
||||
"category": "uncategorized",
|
||||
"name": "bevy-ecs-expert",
|
||||
"description": "Master Bevy's Entity Component System (ECS) in Rust, covering Systems, Queries, Resources, and parallel scheduling.",
|
||||
"risk": "safe",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "billing-automation",
|
||||
"path": "skills/billing-automation",
|
||||
@@ -2024,6 +2096,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "calc",
|
||||
"path": "skills/libreoffice/calc",
|
||||
"category": "libreoffice",
|
||||
"name": "calc",
|
||||
"description": "Spreadsheet creation, format conversion (ODS/XLSX/CSV), formulas, data automation with LibreOffice Calc.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "calendly-automation",
|
||||
"path": "skills/calendly-automation",
|
||||
@@ -2258,6 +2339,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "unknown"
|
||||
},
|
||||
{
|
||||
"id": "cloud-devops",
|
||||
"path": "skills/cloud-devops",
|
||||
"category": "uncategorized",
|
||||
"name": "cloud-devops",
|
||||
"description": "Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "cloud-penetration-testing",
|
||||
"path": "skills/cloud-penetration-testing",
|
||||
@@ -2843,6 +2933,24 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "data-structure-protocol",
|
||||
"path": "skills/data-structure-protocol",
|
||||
"category": "uncategorized",
|
||||
"name": "data-structure-protocol",
|
||||
"description": "Give agents persistent structural memory of a codebase \u2014 navigate dependencies, track public APIs, and understand why connections exist without re-reading the whole repo.",
|
||||
"risk": "safe",
|
||||
"source": "https://github.com/k-kolomeitsev/data-structure-protocol"
|
||||
},
|
||||
{
|
||||
"id": "database",
|
||||
"path": "skills/database",
|
||||
"category": "uncategorized",
|
||||
"name": "database",
|
||||
"description": "Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "database-admin",
|
||||
"path": "skills/database-admin",
|
||||
@@ -2861,15 +2969,6 @@
|
||||
"risk": "unknown",
|
||||
"source": "unknown"
|
||||
},
|
||||
{
|
||||
"id": "database-migrations-sql-migrations",
|
||||
"path": "skills/database-migrations-sql-migrations",
|
||||
"category": "uncategorized",
|
||||
"name": "Database Migrations Sql Migrations",
|
||||
"description": "You are a SQL database migration expert specializing in zero-downtime deployments, data integrity, and production-ready migration strategies for PostgreSQL, MySQL, and SQL Server. Create comprehensive migration scripts with rollback procedures, valid",
|
||||
"risk": "unknown",
|
||||
"source": "unknown"
|
||||
},
|
||||
{
|
||||
"id": "database-optimizer",
|
||||
"path": "skills/database-optimizer",
|
||||
@@ -2915,6 +3014,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "database-migrations-sql-migrations",
|
||||
"path": "skills/database-migrations-sql-migrations",
|
||||
"category": "uncategorized",
|
||||
"name": "database-migrations-sql-migrations",
|
||||
"description": "SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.",
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "datadog-automation",
|
||||
"path": "skills/datadog-automation",
|
||||
@@ -3104,6 +3212,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "development",
|
||||
"path": "skills/development",
|
||||
"category": "uncategorized",
|
||||
"name": "development",
|
||||
"description": "Comprehensive web, mobile, and backend development workflow bundling frontend, backend, full-stack, and mobile development skills for end-to-end application delivery.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "devops-troubleshooter",
|
||||
"path": "skills/devops-troubleshooter",
|
||||
@@ -3194,6 +3311,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "unknown"
|
||||
},
|
||||
{
|
||||
"id": "documentation",
|
||||
"path": "skills/documentation",
|
||||
"category": "uncategorized",
|
||||
"name": "documentation",
|
||||
"description": "Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "documentation-generation-doc-generate",
|
||||
"path": "skills/documentation-generation-doc-generate",
|
||||
@@ -3266,6 +3392,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "draw",
|
||||
"path": "skills/libreoffice/draw",
|
||||
"category": "libreoffice",
|
||||
"name": "draw",
|
||||
"description": "Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "dropbox-automation",
|
||||
"path": "skills/dropbox-automation",
|
||||
@@ -3284,6 +3419,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "unknown"
|
||||
},
|
||||
{
|
||||
"id": "e2e-testing",
|
||||
"path": "skills/e2e-testing",
|
||||
"category": "uncategorized",
|
||||
"name": "e2e-testing",
|
||||
"description": "End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "e2e-testing-patterns",
|
||||
"path": "skills/e2e-testing-patterns",
|
||||
@@ -4058,6 +4202,15 @@
|
||||
"risk": "safe",
|
||||
"source": "https://github.com/go-rod/rod"
|
||||
},
|
||||
{
|
||||
"id": "godot-4-migration",
|
||||
"path": "skills/godot-4-migration",
|
||||
"category": "uncategorized",
|
||||
"name": "godot-4-migration",
|
||||
"description": "Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports.",
|
||||
"risk": "safe",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "godot-gdscript-patterns",
|
||||
"path": "skills/godot-gdscript-patterns",
|
||||
@@ -4409,6 +4562,15 @@
|
||||
"risk": "safe",
|
||||
"source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen"
|
||||
},
|
||||
{
|
||||
"id": "impress",
|
||||
"path": "skills/libreoffice/impress",
|
||||
"category": "libreoffice",
|
||||
"name": "impress",
|
||||
"description": "Presentation creation, format conversion (ODP/PPTX/PDF), slide automation with LibreOffice Impress.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "incident-responder",
|
||||
"path": "skills/incident-responder",
|
||||
@@ -4634,6 +4796,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "kotlin-coroutines-expert",
|
||||
"path": "skills/kotlin-coroutines-expert",
|
||||
"category": "uncategorized",
|
||||
"name": "kotlin-coroutines-expert",
|
||||
"description": "Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing.",
|
||||
"risk": "safe",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "kpi-dashboard-design",
|
||||
"path": "skills/kpi-dashboard-design",
|
||||
@@ -4652,6 +4823,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "unknown"
|
||||
},
|
||||
{
|
||||
"id": "kubernetes-deployment",
|
||||
"path": "skills/kubernetes-deployment",
|
||||
"category": "uncategorized",
|
||||
"name": "kubernetes-deployment",
|
||||
"description": "Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "langchain-architecture",
|
||||
"path": "skills/langchain-architecture",
|
||||
@@ -4796,6 +4976,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "linux-troubleshooting",
|
||||
"path": "skills/linux-troubleshooting",
|
||||
"category": "uncategorized",
|
||||
"name": "linux-troubleshooting",
|
||||
"description": "Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "llm-app-patterns",
|
||||
"path": "skills/llm-app-patterns",
|
||||
@@ -5480,6 +5669,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "office-productivity",
|
||||
"path": "skills/office-productivity",
|
||||
"category": "uncategorized",
|
||||
"name": "office-productivity",
|
||||
"description": "Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "on-call-handoff-patterns",
|
||||
"path": "skills/on-call-handoff-patterns",
|
||||
@@ -5516,6 +5714,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "os-scripting",
|
||||
"path": "skills/os-scripting",
|
||||
"category": "uncategorized",
|
||||
"name": "os-scripting",
|
||||
"description": "Operating system and shell scripting troubleshooting workflow for Linux, macOS, and Windows. Covers bash scripting, system administration, debugging, and automation.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "oss-hunter",
|
||||
"path": "skills/oss-hunter",
|
||||
@@ -5795,6 +6002,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "postgresql-optimization",
|
||||
"path": "skills/postgresql-optimization",
|
||||
"category": "uncategorized",
|
||||
"name": "postgresql-optimization",
|
||||
"description": "PostgreSQL database optimization workflow for query tuning, indexing strategies, performance analysis, and production database management.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "posthog-automation",
|
||||
"path": "skills/posthog-automation",
|
||||
@@ -6002,6 +6218,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "python-fastapi-development",
|
||||
"path": "skills/python-fastapi-development",
|
||||
"category": "uncategorized",
|
||||
"name": "python-fastapi-development",
|
||||
"description": "Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "python-packaging",
|
||||
"path": "skills/python-packaging",
|
||||
@@ -6070,9 +6295,9 @@
|
||||
"path": "skills/rag-implementation",
|
||||
"category": "uncategorized",
|
||||
"name": "rag-implementation",
|
||||
"description": "Build Retrieval-Augmented Generation (RAG) systems for LLM applications with vector databases and semantic search. Use when implementing knowledge-grounded AI, building document Q&A systems, or int...",
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
"description": "RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "react-best-practices",
|
||||
@@ -6119,6 +6344,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "react-nextjs-development",
|
||||
"path": "skills/react-nextjs-development",
|
||||
"category": "uncategorized",
|
||||
"name": "react-nextjs-development",
|
||||
"description": "React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "react-patterns",
|
||||
"path": "skills/react-patterns",
|
||||
@@ -6434,6 +6668,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "unknown"
|
||||
},
|
||||
{
|
||||
"id": "security-audit",
|
||||
"path": "skills/security-audit",
|
||||
"category": "uncategorized",
|
||||
"name": "security-audit",
|
||||
"description": "Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "security-bluebook-builder",
|
||||
"path": "skills/security-bluebook-builder",
|
||||
@@ -6668,6 +6911,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "shader-programming-glsl",
|
||||
"path": "skills/shader-programming-glsl",
|
||||
"category": "uncategorized",
|
||||
"name": "shader-programming-glsl",
|
||||
"description": "Expert guide for writing efficient GLSL shaders (Vertex/Fragment) for web and game engines, covering syntax, uniforms, and common effects.",
|
||||
"risk": "safe",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "sharp-edges",
|
||||
"path": "skills/sharp-edges",
|
||||
@@ -7235,6 +7487,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "unknown"
|
||||
},
|
||||
{
|
||||
"id": "terraform-infrastructure",
|
||||
"path": "skills/terraform-infrastructure",
|
||||
"category": "uncategorized",
|
||||
"name": "terraform-infrastructure",
|
||||
"description": "Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "terraform-module-library",
|
||||
"path": "skills/terraform-module-library",
|
||||
@@ -7289,6 +7550,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "testing-qa",
|
||||
"path": "skills/testing-qa",
|
||||
"category": "uncategorized",
|
||||
"name": "testing-qa",
|
||||
"description": "Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "theme-factory",
|
||||
"path": "skills/theme-factory",
|
||||
@@ -7748,6 +8018,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "web-security-testing",
|
||||
"path": "skills/web-security-testing",
|
||||
"category": "uncategorized",
|
||||
"name": "web-security-testing",
|
||||
"description": "Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "web3-testing",
|
||||
"path": "skills/web3-testing",
|
||||
@@ -7865,6 +8144,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "wordpress",
|
||||
"path": "skills/wordpress",
|
||||
"category": "uncategorized",
|
||||
"name": "wordpress",
|
||||
"description": "Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "wordpress-penetration-testing",
|
||||
"path": "skills/wordpress-penetration-testing",
|
||||
@@ -7874,6 +8162,33 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "wordpress-plugin-development",
|
||||
"path": "skills/wordpress-plugin-development",
|
||||
"category": "uncategorized",
|
||||
"name": "wordpress-plugin-development",
|
||||
"description": "WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, and security best practices.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "wordpress-theme-development",
|
||||
"path": "skills/wordpress-theme-development",
|
||||
"category": "uncategorized",
|
||||
"name": "wordpress-theme-development",
|
||||
"description": "WordPress theme development workflow covering theme architecture, template hierarchy, custom post types, block editor support, and responsive design.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "wordpress-woocommerce-development",
|
||||
"path": "skills/wordpress-woocommerce-development",
|
||||
"category": "uncategorized",
|
||||
"name": "wordpress-woocommerce-development",
|
||||
"description": "WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "workflow-patterns",
|
||||
"path": "skills/workflow-patterns",
|
||||
@@ -7910,6 +8225,15 @@
|
||||
"risk": "unknown",
|
||||
"source": "community"
|
||||
},
|
||||
{
|
||||
"id": "writer",
|
||||
"path": "skills/libreoffice/writer",
|
||||
"category": "libreoffice",
|
||||
"name": "writer",
|
||||
"description": "Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer.",
|
||||
"risk": "safe",
|
||||
"source": "personal"
|
||||
},
|
||||
{
|
||||
"id": "writing-plans",
|
||||
"path": "skills/writing-plans",
|
||||
|
||||
Reference in New Issue
Block a user