Claude Skills by paulasilvatech

Use this skill when the user asks to modernize legacy code with a disciplined GitHub Copilot workflow: brief, assess, map, extract business rules, reimagine architecture, transform modules, and harden with tests and security review. Trigger for COBOL, JCL, legacy Java, .NET, C++, classic ASP, monolith modernization, behavior-preserving rewrite, business-rule extraction, modernization assessment, or legacy-to-modern transformation.

Create an Architectural Decision Record (ADR) as a structured Markdown document with front matter, coded consequences, alternatives, implementation notes, and references. Use when the user asks to document an architecture decision, create an ADR, capture alternatives and trade-offs, or save a decision under docs/adr.

Review, audit, author, and harden GitHub Actions workflows against Actions-specific threats: untrusted-input script injection, privileged trigger escalation, mutable action references, over-scoped GITHUB_TOKEN permissions, unsafe GITHUB_ENV/GITHUB_OUTPUT writes, secret exposure, OIDC misuse, and self-hosted runner risk. Use for .github/workflows/*.yml, secure my CI, pull_request_target danger, SHA pinning, or permissions lockdown.

Apply JUnit 5 best practices for Java tests, including Maven or Gradle setup, standard and parameterized tests, lifecycle hooks, assertions, Mockito isolation, tags, nested tests, and test commands. Use when asked for JUnit 5+ guidance or to write Java unit tests.

Apply Spring Boot best practices for project structure, dependency injection, configuration, REST controllers, DTO validation, services, transactions, Spring Data JPA, logging, testing, and security. Use when asked for Spring Boot guidance or to implement Java backend code.

Extract cited business-rule cards from legacy code, batch jobs, database definitions, screens, and process documents while separating observed behavior from inferred intent. Use when requirements, target design, or behavior-preserving modernization need an evidence-backed rule catalog.

Design and implement characterization, differential, golden-master, and behavior-equivalence tests that pin observable legacy behavior before modernization. Use when a legacy slice needs a trustworthy behavior oracle, regression baseline, or intentional-change record.

Preview, publish, update, inspect, or uninstall managed modernization repository customizations with conflict detection, ownership hashes, transactional rollback, and safe archives. Use when installing a mainframe modernization track's context, stage agents, prompts, instructions, or automation into a target repository.

Analyze Software AG Natural programs, maps, data areas, copycodes, JCL, Adabas DDMs, FDTs, descriptors, MU/PE fields, and call or data dependencies with source citations. Use when reading or inventorying a Natural/Adabas legacy system before modernization.

Review existing PostgreSQL SQL, schema, migrations, functions, triggers, indexes, JSONB, arrays, custom types, domains, extensions, privileges, and Row Level Security for PostgreSQL-specific anti-patterns. Use when asked to audit or critique PostgreSQL code, database migrations, PL/pgSQL, RLS policies, or schema design.

Design, tune, and modernize PostgreSQL SQL, schemas, indexes, functions, and maintenance workflows using PostgreSQL-specific capabilities. Use this skill when the user asks for PostgreSQL optimization, query tuning, JSONB or array design, EXPLAIN ANALYZE interpretation, index strategy, full-text search, custom types, range/geometric types, pg_stat_statements, VACUUM, ANALYZE, partitioning, or secure parameterized database development.

Elicits, normalizes, validates, and traces requirements through a complete Spec-Driven Development workflow using EARS. Use when converting notes, PRDs, legacy evidence, or design inputs into FRD/NFRD, SPECIFICATION.md, architecture and task artifacts, traceability matrices, quality gates, or an implementation-ready SDD handoff.

Defines SIFAP Java 21 and Spring Boot 3.3 backend boundaries, validation, transactions, errors, and data exposure. Use when editing backend Java source.

Defines SIFAP GitHub Actions supply-chain, least-privilege, concurrency, OIDC, and quality-gate rules. Use when editing workflows or composite actions.

Load the SIFAP Natural/Adabas workshop profile, source-evidence boundaries, target stack, traceability contract, and sensitive-data rules. Use when analyzing, specifying, designing, implementing, testing, or operationalizing the SIFAP modernization.

Coordinate the SIFAP modernization workshop through archaeology, architecture, build, and evolution stages with evidence gates, role handoffs, branch intent, and observable completion criteria. Use when starting a stage, checking readiness, or handing work to the next SIFAP stage agent.

Author and validate SIFAP EARS requirements with unique REQ-NNN identifiers, real source_legacy evidence, Given/When/Then acceptance criteria, and test lineage. Use when creating, reviewing, synchronizing, or gating SIFAP specifications and requirement-backed tests.

Defines SIFAP PostgreSQL 16 and Flyway correctness for precision, schema evolution, MU/PE mapping, indexes, and rollback strategy. Use when editing persistence code or migrations.

Defines the SIFAP Next.js 15, React 19, strict TypeScript, accessibility, session, and sensitive-data UI baseline. Use when editing frontend application source.

Defines SIFAP IaC and Azure safety for provider baselines, identity, state, networks, plans, and approvals. Use when editing infrastructure, Compose, or deployment configuration.

Protects SIFAP Natural/Adabas source as evidence and requires dependency-complete, cited analysis. Use when reading legacy members, DDMs, FDTs, maps, copycodes, or JCL.

Requires SIFAP EARS requirements to use REQ-NNN, valid source_legacy evidence, Given/When/Then acceptance criteria, and test lineage. Use when editing specifications or requirement artifacts.

Protects SIFAP authentication, authorization, secrets, CPF, financial data, logs, and untrusted agent context. Use when editing security-sensitive backend, frontend, configuration, or automation.

Requires SIFAP tests to prove requirement and legacy-behavior coverage with deterministic, privacy-safe fixtures. Use when editing backend, frontend, integration, or equivalence tests.

Model Adabas files, DDM and FDT definitions, MU and PE structures, packed and unpacked numerics, descriptors, and ISN identity as a PostgreSQL schema, then prove equivalence with recorded reconciliation numbers. Use when designing or reviewing an Adabas to PostgreSQL data migration, mapping legacy field formats to column types, deciding child-table versus array storage, or verifying that migrated data matches the legacy source.

Use this skill when the user asks to modernize legacy code with a disciplined GitHub Copilot workflow: brief, assess, map, extract business rules, reimagine architecture, transform modules, and harden with tests and security review. Trigger for COBOL, JCL, legacy Java, .NET, C++, classic ASP, monolith modernization, behavior-preserving rewrite, business-rule extraction, modernization assessment, or legacy-to-modern transformation.

Create an Architectural Decision Record (ADR) as a structured Markdown document with front matter, coded consequences, alternatives, implementation notes, and references. Use when the user asks to document an architecture decision, create an ADR, capture alternatives and trade-offs, or save a decision under docs/adr.

Review, audit, author, and harden GitHub Actions workflows against Actions-specific threats: untrusted-input script injection, privileged trigger escalation, mutable action references, over-scoped GITHUB_TOKEN permissions, unsafe GITHUB_ENV/GITHUB_OUTPUT writes, secret exposure, OIDC misuse, and self-hosted runner risk. Use for .github/workflows/*.yml, secure my CI, pull_request_target danger, SHA pinning, or permissions lockdown.

Apply JUnit 5 best practices for Java tests, including Maven or Gradle setup, standard and parameterized tests, lifecycle hooks, assertions, Mockito isolation, tags, nested tests, and test commands. Use when asked for JUnit 5+ guidance or to write Java unit tests.

Apply Spring Boot best practices for project structure, dependency injection, configuration, REST controllers, DTO validation, services, transactions, Spring Data JPA, logging, testing, and security. Use when asked for Spring Boot guidance or to implement Java backend code.

Extract cited business-rule cards from legacy code, batch jobs, database definitions, screens, and process documents while separating observed behavior from inferred intent. Use when requirements, target design, or behavior-preserving modernization need an evidence-backed rule catalog.

Design and implement characterization, differential, golden-master, and behavior-equivalence tests that pin observable legacy behavior before modernization. Use when a legacy slice needs a trustworthy behavior oracle, regression baseline, or intentional-change record.

Preview, publish, update, inspect, or uninstall managed modernization repository customizations with conflict detection, ownership hashes, transactional rollback, and safe archives. Use when installing a mainframe modernization track's context, stage agents, prompts, instructions, or automation into a target repository.

Analyze Software AG Natural programs, maps, data areas, copycodes, JCL, Adabas DDMs, FDTs, descriptors, MU/PE fields, and call or data dependencies with source citations. Use when reading or inventorying a Natural/Adabas legacy system before modernization.

Review existing PostgreSQL SQL, schema, migrations, functions, triggers, indexes, JSONB, arrays, custom types, domains, extensions, privileges, and Row Level Security for PostgreSQL-specific anti-patterns. Use when asked to audit or critique PostgreSQL code, database migrations, PL/pgSQL, RLS policies, or schema design.

Design, tune, and modernize PostgreSQL SQL, schemas, indexes, functions, and maintenance workflows using PostgreSQL-specific capabilities. Use this skill when the user asks for PostgreSQL optimization, query tuning, JSONB or array design, EXPLAIN ANALYZE interpretation, index strategy, full-text search, custom types, range/geometric types, pg_stat_statements, VACUUM, ANALYZE, partitioning, or secure parameterized database development.

Elicits, normalizes, validates, and traces requirements through a complete Spec-Driven Development workflow using EARS. Use when converting notes, PRDs, legacy evidence, or design inputs into FRD/NFRD, SPECIFICATION.md, architecture and task artifacts, traceability matrices, quality gates, or an implementation-ready SDD handoff.

Defines SIFAP Java 21 and Spring Boot 3.3 backend boundaries, validation, transactions, errors, and data exposure. Use when editing backend Java source.

Defines SIFAP GitHub Actions supply-chain, least-privilege, concurrency, OIDC, and quality-gate rules. Use when editing workflows or composite actions.

Defines SIFAP PostgreSQL 16 and Flyway correctness for precision, schema evolution, MU/PE mapping, indexes, and rollback strategy. Use when editing persistence code or migrations.

Defines the SIFAP Next.js 15, React 19, strict TypeScript, accessibility, session, and sensitive-data UI baseline. Use when editing frontend application source.

Defines SIFAP IaC and Azure safety for provider baselines, identity, state, networks, plans, and approvals. Use when editing infrastructure, Compose, or deployment configuration.

Run each SIFAP modernization phase as a bounded correction loop with observable exit gates, an iteration ledger, upstream defect escalation, and a Natural/Adabas engineering graph that proves legacy-to-target coverage. Use when opening or closing a SIFAP phase loop, deciding whether a phase gate passes, routing a defect to the phase that owns its root cause, or building, querying, and gating the modernization graph.

Load the SIFAP Natural/Adabas workshop profile, source-evidence boundaries, target stack, traceability contract, and sensitive-data rules. Use when analyzing, specifying, designing, implementing, testing, or operationalizing the SIFAP modernization.

Protects SIFAP Natural/Adabas source as evidence and requires dependency-complete, cited analysis. Use when reading legacy members, DDMs, FDTs, maps, copycodes, or JCL.

Author and validate SIFAP EARS requirements with unique REQ-NNN identifiers, real source_legacy evidence, Given/When/Then acceptance criteria, and test lineage. Use when creating, reviewing, synchronizing, or gating SIFAP specifications and requirement-backed tests.

Requires SIFAP EARS requirements to use REQ-NNN, valid source_legacy evidence, Given/When/Then acceptance criteria, and test lineage. Use when editing specifications or requirement artifacts.

Protects SIFAP authentication, authorization, secrets, CPF, financial data, logs, and untrusted agent context. Use when editing security-sensitive backend, frontend, configuration, or automation.

Requires SIFAP tests to prove requirement and legacy-behavior coverage with deterministic, privacy-safe fixtures. Use when editing backend, frontend, integration, or equivalence tests.

Coordinate the SIFAP modernization workshop through archaeology, architecture, build, quality, and operations stages with evidence gates, role handoffs, branch intent, and observable completion criteria. Use when starting a stage, checking readiness, or handing work to the next SIFAP stage agent.