dev-software-engineer

Standardize software feature delivery workflows across .NET, C#, Vue, Quasar, and Rust.

2|1|Updated Sep 11, 2025

Search Tags:#workflow #full-stack #inheritance #guidelines #baseline #software-engineering

Ready to run

npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill dev-software-engineer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-software-engineer
Source: https://github.com/ThiagoGuislotti/copilot-instructions/tree/main/.codex/skills/dev-software-engineer
Command: npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill dev-software-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reusable, baseline workflow for software engineering tasks across multiple stacks to speed delivery and ensure consistency.

Core Features & Use Cases

Baseline workflow for feature development, refactoring, and performance tuning across .NET/C#, backend APIs, databases/ORM, frontend Vue/Quasar, and Rust.
Inheritance mechanism: specialized skills can extend this workflow by loading this file first and applying deltas.
Safe, auditable execution context: load minimal context and route to domain instruction packs with clear boundaries.

Quick Start

Load the base skill, then apply domain-specific packs as needed.

Frequently Asked Questions about dev-software-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a baseline full-stack software engineering workflow?▼

A baseline full-stack software engineering workflow provides a standardized, inheritance-friendly process for feature delivery, refactoring, and bug fixes across multiple stacks. It ensures consistent execution by loading minimal context and routing instructions to specific domain packs.

How do I standardize software feature delivery across .NET, Vue, and Rust?▼

You standardize software feature delivery across .NET, Vue, and Rust by applying a baseline workflow that loads minimal context and routes tasks to domain-specific instruction packs. This mechanism ensures safe, auditable changes and consistent execution across diverse technology stacks.

Can I extend a baseline software engineering workflow for specialized tasks?▼

Yes, you can extend a baseline software engineering workflow through an inheritance mechanism. Specialized skills load the base file first and then apply deltas, allowing you to customize the standardized workflow for specific domain packs without altering the original baseline.

Does this baseline workflow support backend APIs and database ORM refactoring?▼

Yes, this baseline workflow explicitly supports backend APIs and database/ORM refactoring. It applies standardized execution workflows and domain instruction routing to ensure safe, auditable changes across backend, frontend, and database layers.

How does domain instruction routing work for full-stack development?▼

Domain instruction routing works for full-stack development by loading minimal context and directing it to specialized domain packs with clear boundaries. This ensures that .NET, Vue/Quasar, or Rust tasks receive targeted instructions while maintaining a safe, auditable execution context.

When do I need an inheritance-friendly workflow for software engineering?▼

You need an inheritance-friendly workflow for software engineering when managing multiple stacks like .NET, Vue, and Rust simultaneously. It provides a reusable baseline that specialized skills can extend, ensuring consistent delivery and safe refactoring without duplicating core workflow logic.