ABLER推進担当
Official@abler-digital-services · Japan
ABLER provides structured documentation and testing frameworks for enterprise system architecture, cloud infrastructure design, and end-to-end quality assurance.
Agent Skills by ABLER推進担当
Showing 28 vetted skills indexed across 1 GitHub repositories.
make-skill-template
Scaffold Agent Skill directories with SKILL.md YAML frontmatter and folder structure.
it-app-e2e-runner
Execute Playwright end-to-end tests and inspect failure artifacts.
req-nf-ops-log-management
Design AWS log management across capture, storage, analysis, and monitoring.
req-fn-app-actor-definition
Define system actors and create an actor definition document for authorization design.
req-nf-inf-availability
Convert availability objectives into SLA-based system availability designs with redundancy and failover specifications.
req-fn-app-business-flow
Generate swimlane business flow diagrams as draw.io XML with Markdown wrappers.
req-nf-pm-grade
Grade non-functional requirements across six categories using structured checklists.
req-fn-app-interface-list
Create structured interface lists mapping data exchanges with external systems.
req-nf-ops-release-management
Generate MECE-structured release management designs with branching, CI/CD, and rollback rules.
req-fn-app-state-transition-diagram
Generate Mermaid or draw.io state-transition diagrams with transition-condition tables.
req-nf-inf-backup-recovery
Design backup and recovery plans with restore procedures aligned to RTO/RPO goals.
req-fn-app-ui-guidelines
Define system-wide UI standards with WCAG 2.1 AA alignment and review checklists.
req-nf-inf-storage
Create and update cloud storage design documents covering EBS, RDS, and S3.
req-fn-app-notification-list
Create a reviewable inventory of system notifications with recipients, triggers, and content.
req-nf-inf-performance
Produce a performance design document with response time, throughput, capacity, and testing criteria.
req-fn-app-process-list
List online UI-triggered server-side actions as structured process records.
it-app-e2e-codegen
Generate Playwright E2E test code from YAML specifications into .spec.ts files.
req-nf-inf-network
Generate and update AWS network design documents covering VPC, routing, and security.
it-app-e2e-spec-writer
Generate YAML end-to-end test specification documents from natural-language scenarios.
req-nf-inf-cloud-services
Creates and updates AWS service design documents with roles, responsibilities, and operational workflows.
req-fn-app-feature-list
Create feature inventories with online screens and batch jobs using F-O-NNN and F-B-NNN IDs.
req-fn-app-system-context-diagram
Generate system context diagrams in draw.io format with Markdown documentation.
req-nf-ops-monitoring
Define monitoring specifications with thresholds, alert notifications, and escalation flows for AWS.
req-nf-inf-server
Generate server design documentation for AP, DB, and storage components.
Frequently Asked Questions About ABLER推進担当
FAQPage SchemaWhat specific tasks can be performed using these system design capabilities?▼
These capabilities enable the generation of technical documentation including system context diagrams, state-transition diagrams, interface lists, and non-functional requirement checklists. You can also produce AWS-specific infrastructure designs covering network, storage, and security, alongside structured inventory lists for features, notifications, and business processes.
Which personas benefit most from these technical design and testing resources?▼
System architects, cloud engineers, and quality assurance specialists benefit from these resources. The structured approach supports technical leads in maintaining consistent documentation for AWS environments and ensures developers can generate standardized test specifications and fixtures for web-based end-to-end verification.
What are the prerequisites for implementing these testing and documentation standards?▼
Implementation requires a foundational understanding of AWS service architecture and Playwright testing frameworks. Users must provide structured YAML specifications or natural-language scenarios to trigger the generation of design documents, test code, or diagrams, ensuring alignment with established project naming conventions and non-functional requirement categories.