devskill 2.0.6 → 2.0.8

package/skills/oo-component-documentation/assets/documentation-template.md

@@ -0,0 +1,97 @@
+---
+title: [Component Name] - Technical Documentation
+component_path: [Source component path]
+version: [Optional version]
+date_created: [YYYY-MM-DD]
+last_updated: [Optional YYYY-MM-DD]
+owner: [Optional team or individual]
+tags: [Optional list of relevant tags]
+---
+
+# [Component Name] Documentation
+
+[Concise introduction describing the component purpose and role in the system.]
+
+## 1. Component Overview
+
+### Purpose/Responsibility
+
+- OVR-001: State the component's primary responsibility
+- OVR-002: Define scope, including included and excluded responsibilities
+- OVR-003: Describe system context and major relationships
+
+## 2. Architecture Section
+
+- ARC-001: Document design patterns used
+- ARC-002: List internal and external dependencies with their purpose
+- ARC-003: Describe component interactions and relationships
+- ARC-004: Include visual diagrams where they clarify structure or behavior
+- ARC-005: Provide a Mermaid diagram showing structure, relationships, and dependencies
+
+### Component Structure and Dependencies Diagram
+
+Show the current:
+
+- Component structure
+- Internal dependencies
+- External dependencies
+- Data flow
+- Inheritance and composition relationships
+
+```mermaid
+graph TD
+    A[Primary Component] --> B[Collaborator]
+    A --> C[Dependency]
+```
+
+## 3. Interface Documentation
+
+- INT-001: Document public interfaces and usage patterns
+- INT-002: Provide a method or property reference table
+- INT-003: Cover events, callbacks, or notification mechanisms when applicable
+
+| Method/Property | Purpose | Parameters | Return Type | Usage Notes |
+|-----------------|---------|------------|-------------|-------------|
+| [Name] | [Purpose] | [Parameters] | [Type] | [Notes] |
+
+## 4. Implementation Details
+
+- IMP-001: Describe main implementation classes and responsibilities
+- IMP-002: Capture configuration requirements and initialization patterns
+- IMP-003: Summarize key algorithms or business logic
+- IMP-004: Note performance characteristics and bottlenecks
+
+## 5. Usage Examples
+
+### Basic Usage
+
+```text
+[Basic usage example aligned with the component language and API]
+```
+
+### Advanced Usage
+
+```text
+[Advanced configuration or orchestration example aligned with the current implementation]
+```
+
+- USE-001: Provide basic usage examples
+- USE-002: Show advanced configuration patterns
+- USE-003: Document best practices and recommended patterns
+
+## 6. Quality Attributes
+
+- QUA-001: Security
+- QUA-002: Performance
+- QUA-003: Reliability
+- QUA-004: Maintainability
+- QUA-005: Extensibility
+
+## 7. Reference Information
+
+- REF-001: List dependencies with versions and purposes where available
+- REF-002: Document configuration options
+- REF-003: Provide testing guidance and mock setup notes
+- REF-004: Capture troubleshooting notes and common issues
+- REF-005: Link related documentation
+- REF-006: Add change history or migration notes when relevant

package/skills/oo-component-documentation/references/create-mode.md

@@ -0,0 +1,32 @@
+# Create mode
+
+Use this workflow when the input is a component source path or the user asks to generate new documentation from code.
+
+## Input handling
+
+- Accept a single file or a folder path representing the component.
+- If the input is a folder, analyze the relevant source files in that folder and nearby supporting files.
+- If the input is a single file, treat it as the primary component entry point and inspect adjacent files as needed to understand collaborators and interfaces.
+
+## Create-specific requirements
+
+- Save the new documentation in `/docs/components/`.
+- Name the file `[component-name]-documentation.md`.
+- Set `component_path` to the source path provided by the user.
+- Set `date_created` to the current date.
+- Set `last_updated` only if the repository convention for the target area expects it at creation time.
+- Populate optional metadata such as `version`, `owner`, and `tags` only when they can be inferred reliably.
+
+## Create-specific analysis focus
+
+- Determine the primary component name and responsibilities from the code structure.
+- Identify the initial system context, scope boundaries, dependencies, design patterns, and collaboration model.
+- Build interface tables and usage examples from the actual public surface area.
+- Create a Mermaid diagram that introduces the component structure, dependencies, and data flow for a reader seeing the documentation for the first time.
+
+## Create-specific output guidance
+
+- Use the full section structure from `../assets/documentation-template.md`.
+- Write the introduction as a fresh overview of what the component does and why it exists.
+- Prefer complete sections over placeholders; if information is unavailable, mark the section with a short limitation note instead of leaving template text behind.
+- Include change history or migration notes only if there is evidence of prior versions or migration concerns in the code or repository history.

package/skills/oo-component-documentation/references/update-mode.md

@@ -0,0 +1,32 @@
+# Update mode
+
+Use this workflow when the input is an existing documentation Markdown file or the user asks to refresh existing component documentation.
+
+## Input handling
+
+- Read the existing documentation first to understand the current structure, terminology, and any front matter metadata.
+- Extract the component source path from the `component_path` front matter when present.
+- If `component_path` is missing, infer the component path from the documentation content and surrounding repository structure.
+- Use the current implementation as the source of truth when the documentation and code disagree.
+
+## Update-specific requirements
+
+- Preserve the existing documentation file as the output target.
+- Preserve `date_created`.
+- Update `last_updated` to the current date.
+- Preserve version history and ownership metadata when still accurate; refresh them only when the code or repository evidence indicates they have changed.
+- Maintain the existing organization where it is still useful, but ensure the content remains consistent with the shared template expectations.
+
+## Update-specific analysis focus
+
+- Compare the existing documentation with the current code to identify stale APIs, outdated diagrams, renamed dependencies, and changed usage patterns.
+- Highlight breaking changes, deprecated features, or major architectural shifts when they are evident.
+- Refresh method tables, examples, diagrams, dependency lists, and quality attribute notes to match the implementation as it exists today.
+- Add missing sections only when the component has grown or the current documentation omits information now needed for maintainers.
+
+## Update-specific output guidance
+
+- Keep useful editorial choices from the existing document, but remove stale or misleading content.
+- Update examples so they compile conceptually against the current API shape.
+- Refresh Mermaid diagrams rather than replacing them with generic placeholders.
+- Add migration notes or change history when the update reveals important compatibility or behavior changes.

package/skills/openapi-to-application-code/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/openapi-to-application-code/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: openapi-to-application-code
+description: 'Generate a complete, production-ready application from an OpenAPI specification'
+---
+
+# Generate Application from OpenAPI Spec
+
+Your goal is to generate a complete, working application from an OpenAPI specification using the active framework's conventions and best practices.
+
+## Input Requirements
+
+1. **OpenAPI Specification**: Provide either:
+   - A URL to the OpenAPI spec (e.g., `https://api.example.com/openapi.json`)
+   - A local file path to the OpenAPI spec
+   - The full OpenAPI specification content pasted directly
+
+2. **Project Details** (if not in spec):
+   - Project name and description
+   - Target framework and version
+   - Package/namespace naming conventions
+   - Authentication method (if not specified in OpenAPI)
+
+## Generation Process
+
+### Step 1: Analyze the OpenAPI Specification
+- Validate the OpenAPI spec for completeness and correctness
+- Identify all endpoints, HTTP methods, request/response schemas
+- Extract authentication requirements and security schemes
+- Note data model relationships and constraints
+- Flag any ambiguities or incomplete definitions
+
+### Step 2: Design Application Architecture
+- Plan directory structure appropriate for the framework
+- Identify controller/handler grouping by resource or domain
+- Design service layer organization for business logic
+- Plan data models and entity relationships
+- Design configuration and initialization strategy
+
+### Step 3: Generate Application Code
+- Create project structure with build/package configuration files
+- Generate models/DTOs from OpenAPI schemas
+- Generate controllers/handlers with route mappings
+- Generate service layer with business logic
+- Generate repository/data access layer if applicable
+- Add error handling, validation, and logging
+- Generate configuration and startup code
+
+### Step 4: Add Supporting Files
+- Generate appropriate unit tests for services and controllers
+- Create README with setup and running instructions
+- Add .gitignore and environment configuration templates
+- Generate API documentation files
+- Create example requests/integration tests
+
+## Output Structure
+
+The generated application will include:
+
+```
+project-name/
+├── README.md                      # Setup and usage instructions
+├── [build-config]                 # Framework-specific build files (pom.xml, build.gradle, package.json, etc.)
+├── src/
+│   ├── main/
+│   │   ├── [language]/
+│   │   │   ├── controllers/       # HTTP endpoint handlers
+│   │   │   ├── services/          # Business logic
+│   │   │   ├── models/            # Data models and DTOs
+│   │   │   ├── repositories/      # Data access (if applicable)
+│   │   │   └── config/            # Application configuration
+│   │   └── resources/             # Configuration files
+│   └── test/
+│       ├── [language]/
+│       │   ├── controllers/       # Controller tests
+│       │   └── services/          # Service tests
+│       └── resources/             # Test configuration
+├── .gitignore
+├── .env.example                   # Environment variables template
+└── docker-compose.yml             # Optional: Docker setup (if applicable)
+```
+
+## Best Practices Applied
+
+- **Framework Conventions**: Follows framework-specific naming, structure, and patterns
+- **Separation of Concerns**: Clear layers with controllers, services, and repositories
+- **Error Handling**: Comprehensive error handling with meaningful responses
+- **Validation**: Input validation and schema validation throughout
+- **Logging**: Structured logging for debugging and monitoring
+- **Testing**: Unit tests for services and controllers
+- **Documentation**: Inline code documentation and setup instructions
+- **Security**: Implements authentication/authorization from OpenAPI spec
+- **Scalability**: Design patterns support growth and maintenance
+
+## Next Steps
+
+After generation:
+
+1. Review the generated code structure and make customizations as needed
+2. Install dependencies according to framework requirements
+3. Configure environment variables and database connections
+4. Run tests to verify generated code
+5. Start the development server
+6. Test endpoints using the provided examples
+
+## Questions to Ask if Needed
+
+- Should the application include database/ORM setup, or just in-memory/mock data?
+- Do you want Docker configuration for containerization?
+- Should authentication be JWT, OAuth2, API keys, or basic auth?
+- Do you need integration tests or just unit tests?
+- Any specific database technology preferences?
+- Should the API include pagination, filtering, and sorting examples?

package/skills/openapi-to-application-code/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/openapi-to-application-code`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/pdf/LICENSE.txt

@@ -0,0 +1,30 @@
+© 2025 Anthropic, PBC. All rights reserved.
+
+LICENSE: Use of these materials (including all code, prompts, assets, files,
+and other components of this Skill) is governed by your agreement with
+Anthropic regarding use of Anthropic's services. If no separate agreement
+exists, use is governed by Anthropic's Consumer Terms of Service or
+Commercial Terms of Service, as applicable:
+https://www.anthropic.com/legal/consumer-terms
+https://www.anthropic.com/legal/commercial-terms
+Your applicable agreement is referred to as the "Agreement." "Services" are
+as defined in the Agreement.
+
+ADDITIONAL RESTRICTIONS: Notwithstanding anything in the Agreement to the
+contrary, users may not:
+
+- Extract these materials from the Services or retain copies of these
+  materials outside the Services
+- Reproduce or copy these materials, except for temporary copies created
+  automatically during authorized use of the Services
+- Create derivative works based on these materials
+- Distribute, sublicense, or transfer these materials to any third party
+- Make, offer to sell, sell, or import any inventions embodied in these
+  materials
+- Reverse engineer, decompile, or disassemble these materials
+
+The receipt, viewing, or possession of these materials does not convey or
+imply any license or right beyond those expressly granted above.
+
+Anthropic retains all right, title, and interest in these materials,
+including all copyrights, patents, and other intellectual property rights.

package/skills/pdf/SKILL.md

@@ -0,0 +1,314 @@
+---
+name: pdf
+description: Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
+license: Proprietary. LICENSE.txt has complete terms
+---
+
+# PDF Processing Guide
+
+## Overview
+
+This guide covers essential PDF processing operations using Python libraries and command-line tools. For advanced features, JavaScript libraries, and detailed examples, see REFERENCE.md. If you need to fill out a PDF form, read FORMS.md and follow its instructions.
+
+## Quick Start
+
+```python
+from pypdf import PdfReader, PdfWriter
+
+# Read a PDF
+reader = PdfReader("document.pdf")
+print(f"Pages: {len(reader.pages)}")
+
+# Extract text
+text = ""
+for page in reader.pages:
+    text += page.extract_text()
+```
+
+## Python Libraries
+
+### pypdf - Basic Operations
+
+#### Merge PDFs
+```python
+from pypdf import PdfWriter, PdfReader
+
+writer = PdfWriter()
+for pdf_file in ["doc1.pdf", "doc2.pdf", "doc3.pdf"]:
+    reader = PdfReader(pdf_file)
+    for page in reader.pages:
+        writer.add_page(page)
+
+with open("merged.pdf", "wb") as output:
+    writer.write(output)
+```
+
+#### Split PDF
+```python
+reader = PdfReader("input.pdf")
+for i, page in enumerate(reader.pages):
+    writer = PdfWriter()
+    writer.add_page(page)
+    with open(f"page_{i+1}.pdf", "wb") as output:
+        writer.write(output)
+```
+
+#### Extract Metadata
+```python
+reader = PdfReader("document.pdf")
+meta = reader.metadata
+print(f"Title: {meta.title}")
+print(f"Author: {meta.author}")
+print(f"Subject: {meta.subject}")
+print(f"Creator: {meta.creator}")
+```
+
+#### Rotate Pages
+```python
+reader = PdfReader("input.pdf")
+writer = PdfWriter()
+
+page = reader.pages[0]
+page.rotate(90)  # Rotate 90 degrees clockwise
+writer.add_page(page)
+
+with open("rotated.pdf", "wb") as output:
+    writer.write(output)
+```
+
+### pdfplumber - Text and Table Extraction
+
+#### Extract Text with Layout
+```python
+import pdfplumber
+
+with pdfplumber.open("document.pdf") as pdf:
+    for page in pdf.pages:
+        text = page.extract_text()
+        print(text)
+```
+
+#### Extract Tables
+```python
+with pdfplumber.open("document.pdf") as pdf:
+    for i, page in enumerate(pdf.pages):
+        tables = page.extract_tables()
+        for j, table in enumerate(tables):
+            print(f"Table {j+1} on page {i+1}:")
+            for row in table:
+                print(row)
+```
+
+#### Advanced Table Extraction
+```python
+import pandas as pd
+
+with pdfplumber.open("document.pdf") as pdf:
+    all_tables = []
+    for page in pdf.pages:
+        tables = page.extract_tables()
+        for table in tables:
+            if table:  # Check if table is not empty
+                df = pd.DataFrame(table[1:], columns=table[0])
+                all_tables.append(df)
+
+# Combine all tables
+if all_tables:
+    combined_df = pd.concat(all_tables, ignore_index=True)
+    combined_df.to_excel("extracted_tables.xlsx", index=False)
+```
+
+### reportlab - Create PDFs
+
+#### Basic PDF Creation
+```python
+from reportlab.lib.pagesizes import letter
+from reportlab.pdfgen import canvas
+
+c = canvas.Canvas("hello.pdf", pagesize=letter)
+width, height = letter
+
+# Add text
+c.drawString(100, height - 100, "Hello World!")
+c.drawString(100, height - 120, "This is a PDF created with reportlab")
+
+# Add a line
+c.line(100, height - 140, 400, height - 140)
+
+# Save
+c.save()
+```
+
+#### Create PDF with Multiple Pages
+```python
+from reportlab.lib.pagesizes import letter
+from reportlab.platypus import SimpleDocTemplate, Paragraph, Spacer, PageBreak
+from reportlab.lib.styles import getSampleStyleSheet
+
+doc = SimpleDocTemplate("report.pdf", pagesize=letter)
+styles = getSampleStyleSheet()
+story = []
+
+# Add content
+title = Paragraph("Report Title", styles['Title'])
+story.append(title)
+story.append(Spacer(1, 12))
+
+body = Paragraph("This is the body of the report. " * 20, styles['Normal'])
+story.append(body)
+story.append(PageBreak())
+
+# Page 2
+story.append(Paragraph("Page 2", styles['Heading1']))
+story.append(Paragraph("Content for page 2", styles['Normal']))
+
+# Build PDF
+doc.build(story)
+```
+
+#### Subscripts and Superscripts
+
+**IMPORTANT**: Never use Unicode subscript/superscript characters (₀₁₂₃₄₅₆₇₈₉, ⁰¹²³⁴⁵⁶⁷⁸⁹) in ReportLab PDFs. The built-in fonts do not include these glyphs, causing them to render as solid black boxes.
+
+Instead, use ReportLab's XML markup tags in Paragraph objects:
+```python
+from reportlab.platypus import Paragraph
+from reportlab.lib.styles import getSampleStyleSheet
+
+styles = getSampleStyleSheet()
+
+# Subscripts: use <sub> tag
+chemical = Paragraph("H<sub>2</sub>O", styles['Normal'])
+
+# Superscripts: use <super> tag
+squared = Paragraph("x<super>2</super> + y<super>2</super>", styles['Normal'])
+```
+
+For canvas-drawn text (not Paragraph objects), manually adjust font the size and position rather than using Unicode subscripts/superscripts.
+
+## Command-Line Tools
+
+### pdftotext (poppler-utils)
+```bash
+# Extract text
+pdftotext input.pdf output.txt
+
+# Extract text preserving layout
+pdftotext -layout input.pdf output.txt
+
+# Extract specific pages
+pdftotext -f 1 -l 5 input.pdf output.txt  # Pages 1-5
+```
+
+### qpdf
+```bash
+# Merge PDFs
+qpdf --empty --pages file1.pdf file2.pdf -- merged.pdf
+
+# Split pages
+qpdf input.pdf --pages . 1-5 -- pages1-5.pdf
+qpdf input.pdf --pages . 6-10 -- pages6-10.pdf
+
+# Rotate pages
+qpdf input.pdf output.pdf --rotate=+90:1  # Rotate page 1 by 90 degrees
+
+# Remove password
+qpdf --password=mypassword --decrypt encrypted.pdf decrypted.pdf
+```
+
+### pdftk (if available)
+```bash
+# Merge
+pdftk file1.pdf file2.pdf cat output merged.pdf
+
+# Split
+pdftk input.pdf burst
+
+# Rotate
+pdftk input.pdf rotate 1east output rotated.pdf
+```
+
+## Common Tasks
+
+### Extract Text from Scanned PDFs
+```python
+# Requires: pip install pytesseract pdf2image
+import pytesseract
+from pdf2image import convert_from_path
+
+# Convert PDF to images
+images = convert_from_path('scanned.pdf')
+
+# OCR each page
+text = ""
+for i, image in enumerate(images):
+    text += f"Page {i+1}:\n"
+    text += pytesseract.image_to_string(image)
+    text += "\n\n"
+
+print(text)
+```
+
+### Add Watermark
+```python
+from pypdf import PdfReader, PdfWriter
+
+# Create watermark (or load existing)
+watermark = PdfReader("watermark.pdf").pages[0]
+
+# Apply to all pages
+reader = PdfReader("document.pdf")
+writer = PdfWriter()
+
+for page in reader.pages:
+    page.merge_page(watermark)
+    writer.add_page(page)
+
+with open("watermarked.pdf", "wb") as output:
+    writer.write(output)
+```
+
+### Extract Images
+```bash
+# Using pdfimages (poppler-utils)
+pdfimages -j input.pdf output_prefix
+
+# This extracts all images as output_prefix-000.jpg, output_prefix-001.jpg, etc.
+```
+
+### Password Protection
+```python
+from pypdf import PdfReader, PdfWriter
+
+reader = PdfReader("input.pdf")
+writer = PdfWriter()
+
+for page in reader.pages:
+    writer.add_page(page)
+
+# Add password
+writer.encrypt("userpassword", "ownerpassword")
+
+with open("encrypted.pdf", "wb") as output:
+    writer.write(output)
+```
+
+## Quick Reference
+
+| Task | Best Tool | Command/Code |
+|------|-----------|--------------|
+| Merge PDFs | pypdf | `writer.add_page(page)` |
+| Split PDFs | pypdf | One page per file |
+| Extract text | pdfplumber | `page.extract_text()` |
+| Extract tables | pdfplumber | `page.extract_tables()` |
+| Create PDFs | reportlab | Canvas or Platypus |
+| Command line merge | qpdf | `qpdf --empty --pages ...` |
+| OCR scanned PDFs | pytesseract | Convert to image first |
+| Fill PDF forms | pdf-lib or pypdf (see FORMS.md) | See FORMS.md |
+
+## Next Steps
+
+- For advanced pypdfium2 usage, see REFERENCE.md
+- For JavaScript libraries (pdf-lib), see REFERENCE.md
+- If you need to fill out a PDF form, follow the instructions in FORMS.md
+- For troubleshooting guides, see REFERENCE.md

package/skills/pdf/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/anthropics/skills/pdf`
+- **Git SHA:** `887114fd09f8f24a7e6c907f9ee505348498ab6a`
+- **Synced:** 2026-03-24