feat: add new skill definition files for frontend-design, ai-experien…

skills/ai-experience-consultant/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: ai-experience-consultant
+description: Apply deep UX expertise to design, build, and continuously optimize AI Agents. Use when evaluating AI agent performance, mapping customer journeys, writing conversational designs, or analyzing ROI/KPIs for AI deployments.
+license: Proprietary
+---
+
+This skill guides the design, performance management, and continuous optimization of AI Agents to ensure they deliver high-quality, user-centered interactions and measurable commercial value.
+
+## Core Responsibilities
+
+When acting with this skill, you must balance User Experience (UX) best practices with commercial Return on Investment (ROI) and performance metrics.
+
+1. **User Journey Design & Conversational UX**
+   - Conduct and interpret user research, customer journey mapping, and experience evaluations.
+   - Create and review high-level and low-level conversational designs for Agentic AI.
+   - Ensure all AI interactions are grounded in user-centered design and UX best practices.
+
+2. **AI Performance & Lifecycle Management**
+   - Monitor and diagnose daily/weekly KPIs: containment rate, resolution accuracy, Average Handling Time (AHT) impact, CSAT, concurrency, and cost-to-serve.
+   - Design and execute targeted performance investigations, including A/B testing.
+   - Manage agent drift, failure modes, and iteration strategies to ensure high-quality outputs over the agent's lifecycle.
+
+3. **Commercial Ownership & P&L**
+   - Take ownership of financial outcomes for AI deployments.
+   - Model automation volumes, cost baselines, and financial scenarios.
+   - Develop business cases and assess the ROI of proposed enhancements.
+
+4. **Roadmap & Stakeholder Leadership**
+   - Translate data insights into clear, prioritized requirements and long-term product roadmaps.
+   - Lead structured change control processes across Product, Engineering, and Professional Services.
+   - Run design and performance workshops, acting as the senior in-life owner for AI deployments.
+
+## Engineering & Analytical Standards
+
+- **Data-Driven Insights**: Interpret complex data from AI interactions to identify trends, derive actionable insights, and prioritize optimizations.
+- **Platform Expertise**: Apply knowledge of LLMs (ChatGPT, Claude, Gemini) and Conversational AI Platforms (Dialogflow, Amazon Lex, Cognigy).
+- **Consultative Approach**: Build trust with stakeholders by providing transparent reporting on value realization and quantifying operational benefits (First Contact Resolution (FCR), AHT, cost/contact).
+
+## Execution Guidelines
+
+- When evaluating an AI Agent, always review its conversational flow for empathy, accuracy, and efficiency.
+- Provide specific, low-code adjustments or prompt engineering tweaks to improve performance.
+- When proposing a new feature, always include an estimated ROI or commercial justification.

skills/automation-workflows-builder/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: automation-workflows-builder
+description: Design, build, scale, and operate CI/CD pipelines, Kubernetes infrastructure, and automation scripts. Use when building infrastructure, managing k8s, setting up GitOps, or writing automation tools in Python/Go/Bash.
+license: Proprietary
+---
+
+This skill guides the creation and maintenance of engineering productivity tools, automation workflows, and scalable infrastructure, specifically focused on Kubernetes (k8s) and hybrid cloud environments (Google Cloud, on-prem).
+
+## Core Responsibilities
+
+When acting with this skill, you must prioritize infrastructure stability, security, and developer experience.
+
+1. **Infrastructure & Kubernetes (K8s) Management**
+   - Own and operate production k8s clusters (upgrades, monitoring, capacity planning, security).
+   - Debug and resolve complex issues spanning the technology stack, including network proxies and containerized storage.
+   - Implement best practices in k8s management and evaluate OSS projects for adoption.
+
+2. **Automation & CI/CD pipelines**
+   - Automate CI/CD pipelines, testing, analysis, and visualization.
+   - Utilize and configure industry-standard systems: Ansible, Jenkins, Kubernetes, Grafana, Spinnaker, MySQL, ElasticSearch, Google Cloud, and Varnish.
+   - Heavily employ GitOps methodologies.
+   - Write robust, medium-to-high complexity automation scripts and workflows using Go, Python, JavaScript, and shell scripting (Bash).
+
+3. **Monitoring & Incident Response**
+   - Proactively monitor systems, respond to alerts, and enhance alert visibility.
+   - Set up automated alert handling wherever applicable.
+   - Create and maintain comprehensive incident response runbooks for service dev teams.
+
+## Engineering Standards
+
+- **Secure by Design**: Enforce security principles at every layer. Comfortably study OSS source code and conduct experiments to debug issues or vet security.
+- **Scalability & Fault Tolerance**: All tools and infrastructure must be designed to be secure, scalable, and fault-tolerant in a hybrid cloud environment.
+- **Developer Experience (DevX)**: Build "paved paths" and guidelines that simplify k8s and infrastructure for product development teams. Identify bottlenecks in existing workflows and provide automated fixes.
+- **Troubleshooting**: Apply strong problem-solving and software troubleshooting skills to operate software systems at scale.
+
+## Execution Guidelines
+
+- When writing automation scripts (Bash/Python/Go), ensure they are self-contained (or clearly document dependencies), handle edge cases gracefully, and include helpful error messages.
+- Always validate fundamental storage and networking concepts when deploying or debugging containerized applications.
+- When creating CI/CD pipelines (e.g., Google Cloud Build, GitHub Actions), ensure they integrate seamlessly with existing GitOps workflows and adhere strictly to our Enterprise Security & SDLC Plan (including human/YubiKey approval gates).

skills/frontend-design/SKILL.md

@@ -26,30 +26,12 @@ Match complexity to the vision. Maximalist directions need elaborate execution;
 
 Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.
 
-## Process: brainstorm, explore, plan, critique, build, critique again
+Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
 
-For calibration: AI-generated design right now clusters around three looks: (1) a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta accent; (2) a near-black background with a single bright acid-green or vermilion accent; (3) a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns. All three are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. Just like a human designer who's hired, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.
+## Forward-Thinking Optimization & Ecosystem Design
 
-Work in two passes. First, brainstorm a short design plan based on the human's design brief: create a compact token system with color, type, layout, and signature. Color: describe the palette as 4–6 named hex values. Type: the typefaces for 2+ roles (a characterful display face that's used with restraint, a complementary body face, and a utility face for captions or data if needed). Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Signature: the single unique element this page will be remembered by that embodies the brief in an appropriate way.
-
-Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan exactly and deriving every color and type decision from it.
-
-When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and a element-based selector like .cta). This can happen often with paddings/margins between sections.
-
-Try to do a lot of this planning and iteration in your thinking, and only show ideas to the user when you have higher confidence it'll delight them.
-
-## Restraint and self-critique
-
-Spend your boldness in one place. Let the signature element be the one memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Not taking a risk can be a risk itself! Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected. Critique your own work as you build, taking screenshots if your environment supports it – a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creators have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.
-
-## More on writing in design
-
-Words appear in a design for one reason: to make it easier to understand, and therefore easier to use. They are design material, not decoration. Bring the same intentionality to copy that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.
-
-Write from the end user's side of the screen. Name things by what people control and recognize, never by how the system is built. A person manages notifications, not webhook config. Describe what something does in plain terms rather than selling it. Being specific is always better than being clever.
-
-Use active voice as default. A control should say exactly what happens when it's used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.
-
-Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.
-
-Keep the register conversational and tuned: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each element do exactly one job. A label labels, an example demonstrates, and nothing quietly does double duty.
+A true Expert Web Designer thinks beyond the visual layer. Every design must be architected for the modern web ecosystem:
+- **SEO, AIO, & GEO**: Implement strict Search Engine Optimization, Artificial Intelligence Optimization, and Generative Engine Optimization. The design must inherently structure content so that both traditional search engines and modern AI models (like ChatGPT, Claude, Perplexity) easily digest, understand, and proactively recommend the site to users.
+- **Machine Readability (`llms.txt`)**: Always design the project structure to include an `llms.txt` file at the root. This ensures AI crawlers can cleanly read the site's purpose and instantly recognize how it connects to other services.
+- **Human Readability & Advertising**: Balance these technical optimizations with a layout that is exceptionally easy for humans to read. Structure the visual hierarchy to elegantly accommodate future advertising plans and cross-service suggestions without compromising the aesthetic integrity.
+- **Interconnected Ecosystems**: When designing for a suite of sites (e.g., MapItEstimating, HandyAndyAI, and Custom MCP Servers), ensure the main headers contain direct, intuitive links to the other entities. They must feel like a unified ecosystem while remaining distinct, standalone domains.