@totaland/create-starter-kit 2.0.1 → 2.0.2

package/templates/frontend/.github/instructions/task-implementation.instructions.md

@@ -1,190 +0,0 @@
----
-applyTo: '**/.copilot-tracking/changes/*.md'
-description: 'Instructions for implementing task plans with progressive tracking and change record - Brought to you by microsoft/edge-ai'
----
-
-# Task Plan Implementation Instructions
-
-You will implement your specific task plan located in `.copilot-tracking/plans/**` and `.copilot-tracking/details/**`. Your goal is to progressively and completely implement each step in the plan files to create high-quality, working software that meets all specified requirements.
-
-Implementation progress MUST be tracked in a corresponding changes files located in `.copilot-tracking/changes/**`.
-
-## Core Implementation Process
-
-### 1. Plan Analysis and Preparation
-
-**MUST complete before starting implementation:**
-- **MANDATORY**: Read and fully understand the complete plan file including scope, objectives, all phases, and every checklist item
-- **MANDATORY**: Read and fully understand the corresponding changes file completely - if any parts are missing from context, read the entire file back in using `read_file`
-- **MANDATORY**: Identify all referenced files mentioned in the plan and examine them for context
-- **MANDATORY**: Understand current project structure and conventions
-
-### 2. Systematic Implementation Process
-
-**Implement each task in the plan systematically:**
-
-1. **Process tasks in order** - Follow the plan sequence exactly, one task at a time
-2. **MANDATORY before implementing any task:**
-   - **ALWAYS ensure implementation is associated with a specific task from the plan**
-   - **ALWAYS read the entire details section for that task from the associated details markdown file in `.copilot-tracking/details/**`**
-   - **FULLY understand all implementation details before proceeding**
-   - Gather any additional required context as needed
-
-3. **Implement the task completely with working code:**
-   - Follow existing code patterns and conventions from the workspace
-   - Create working functionality that meets all task requirements specified in the details
-   - Include proper error handling, documentation, and follow best practices
-
-4. **Mark task complete and update changes tracking:**
-   - Update plan file: change `[ ]` to `[x]` for completed task
-   - **MANDATORY after completing EVERY task**: Update the changes file by appending to the appropriate Added, Modified, or Removed sections with relative file paths and one-sentence summary of what was implemented
-   - **MANDATORY**: If any changes diverge from the task plan and details, specifically call out within the relevant section that the change was made outside of the plan and include the specific reason
-   - If ALL tasks in a phase are complete `[x]`, mark the phase header as complete `[x]`
-
-### 3. Implementation Quality Standards
-
-**Every implementation MUST:**
-- Follow existing workspace patterns and conventions (check `copilot/` folder for standards)
-- Implement complete, working functionality that meets all task requirements
-- Include appropriate error handling and validation
-- Use consistent naming conventions and code structure from the workspace
-- Add necessary documentation and comments for complex logic
-- Ensure compatibility with existing systems and dependencies
-
-### 4. Continuous Progress and Validation
-
-**After implementing each task:**
-1. Validate the changes made against the task requirements from the details file
-2. Fix any problems before moving to the next task
-3. **MANDATORY**: Update the plan file to mark completed tasks `[x]`
-4. **MANDATORY after EVERY task completion**: Update the changes file by appending to Added, Modified, or Removed sections with relative file paths and one-sentence summary of what was implemented
-5. Continue to the next unchecked task
-
-**Continue until:**
-- All tasks in the plan are marked complete `[x]`
-- All specified files have been created or updated with working code
-- All success criteria from the plan have been verified
-
-### 5. Reference Gathering Guidelines
-
-**When gathering external references:**
-- Focus on practical implementation examples over theoretical documentation
-- Validate that external sources contain actual usable patterns
-- Adapt external patterns to match workspace conventions and standards
-
-**When implementing from references:**
-- Follow workspace patterns and conventions first, external patterns second
-- Implement complete, working functionality rather than just examples
-- Ensure all dependencies and configurations are properly integrated
-- Ensure implementations work within the existing project structure
-
-### 6. Completion and Documentation
-
-**Implementation is complete when:**
-- All plan tasks are marked complete `[x]`
-- All specified files exist with working code
-- All success criteria from the plan are verified
-- No implementation errors remain
-
-**Final step - update changes file with release summary:**
-- Add Release Summary section only after ALL phases are marked complete `[x]`
-- Document complete file inventory and overall implementation summary for release documentation
-
-### 7. Problem Resolution
-
-**When encountering implementation issues:**
-- Document the specific problem clearly
-- Try alternative approaches or search terms
-- Use workspace patterns as fallback when external references fail
-- Continue with available information rather than stopping completely
-- Note any unresolved issues in the plan file for future reference
-
-## Implementation Workflow
-
-```
-1. Read and fully understand plan file and all checklists completely
-2. Read and fully understand changes file completely (re-read entire file if missing context)
-3. For each unchecked task:
-   a. Read entire details section for that task from details markdown file
-   b. Fully understand all implementation requirements
-   c. Implement task with working code following workspace patterns
-   d. Validate implementation meets task requirements
-   e. Mark task complete [x] in plan file
-   f. Update changes file with Added, Modified, or Removed entries
-   g. Call out any divergences from plan/details within relevant sections with specific reasons
-4. Repeat until all tasks complete
-5. Only after ALL phases are complete [x]: Add final Release Summary to changes file
-```
-
-## Success Criteria
-
-Implementation is complete when:
-- ✅ All plan tasks are marked complete `[x]`
-- ✅ All specified files contain working code
-- ✅ Code follows workspace patterns and conventions
-- ✅ All functionality works as expected within the project
-- ✅ Changes file is updated after every task completion with Added, Modified, or Removed entries
-- ✅ Changes file documents all phases with detailed release-ready documentation and final release summary
-
-## Template Changes File
-
-Use the following as a template for the changes file that tracks implementation progress for releases.
-Replace `{{ }}` with appropriate values. Create this file in `./.copilot-tracking/changes/` with filename: `YYYYMMDD-task-description-changes.md`
-
-**IMPORTANT**: Update this file after EVERY task completion by appending to Added, Modified, or Removed sections.
-**MANDATORY**: Always include the following at the top of the changes file: `<!-- markdownlint-disable-file -->`
-
-<!-- <changes-template> -->
-```markdown
-<!-- markdownlint-disable-file -->
-# Release Changes: {{task name}}
-
-**Related Plan**: {{plan-file-name}}
-**Implementation Date**: {{YYYY-MM-DD}}
-
-## Summary
-
-{{Brief description of the overall changes made for this release}}
-
-## Changes
-
-### Added
-
-- {{relative-file-path}} - {{one sentence summary of what was implemented}}
-
-### Modified
-
-- {{relative-file-path}} - {{one sentence summary of what was changed}}
-
-### Removed
-
-- {{relative-file-path}} - {{one sentence summary of what was removed}}
-
-## Release Summary
-
-**Total Files Affected**: {{number}}
-
-### Files Created ({{count}})
-
-- {{file-path}} - {{purpose}}
-
-### Files Modified ({{count}})
-
-- {{file-path}} - {{changes-made}}
-
-### Files Removed ({{count}})
-
-- {{file-path}} - {{reason}}
-
-### Dependencies & Infrastructure
-
-- **New Dependencies**: {{list-of-new-dependencies}}
-- **Updated Dependencies**: {{list-of-updated-dependencies}}
-- **Infrastructure Changes**: {{infrastructure-updates}}
-- **Configuration Updates**: {{configuration-changes}}
-
-### Deployment Notes
-
-{{Any specific deployment considerations or steps}}
-```
-<!-- </changes-template> -->

package/templates/frontend/.github/instructions/typescript-mcp-server.instructions.md

@@ -1,228 +0,0 @@
----
-description: 'Instructions for building Model Context Protocol (MCP) servers using the TypeScript SDK'
-applyTo: '**/*.ts, **/*.js, **/package.json'
----
-
-# TypeScript MCP Server Development
-
-## Instructions
-
-- Use the **@modelcontextprotocol/sdk** npm package: `npm install @modelcontextprotocol/sdk`
-- Import from specific paths: `@modelcontextprotocol/sdk/server/mcp.js`, `@modelcontextprotocol/sdk/server/stdio.js`, etc.
-- Use `McpServer` class for high-level server implementation with automatic protocol handling
-- Use `Server` class for low-level control with manual request handlers
-- Use **zod** for input/output schema validation: `npm install zod@3`
-- Always provide `title` field for tools, resources, and prompts for better UI display
-- Use `registerTool()`, `registerResource()`, and `registerPrompt()` methods (recommended over older APIs)
-- Define schemas using zod: `{ inputSchema: { param: z.string() }, outputSchema: { result: z.string() } }`
-- Return both `content` (for display) and `structuredContent` (for structured data) from tools
-- For HTTP servers, use `StreamableHTTPServerTransport` with Express or similar frameworks
-- For local integrations, use `StdioServerTransport` for stdio-based communication
-- Create new transport instances per request to prevent request ID collisions (stateless mode)
-- Use session management with `sessionIdGenerator` for stateful servers
-- Enable DNS rebinding protection for local servers: `enableDnsRebindingProtection: true`
-- Configure CORS headers and expose `Mcp-Session-Id` for browser-based clients
-- Use `ResourceTemplate` for dynamic resources with URI parameters: `new ResourceTemplate('resource://{param}', { list: undefined })`
-- Support completions for better UX using `completable()` wrapper from `@modelcontextprotocol/sdk/server/completable.js`
-- Implement sampling with `server.server.createMessage()` to request LLM completions from clients
-- Use `server.server.elicitInput()` to request additional user input during tool execution
-- Enable notification debouncing for bulk updates: `debouncedNotificationMethods: ['notifications/tools/list_changed']`
-- Dynamic updates: call `.enable()`, `.disable()`, `.update()`, or `.remove()` on registered items to emit `listChanged` notifications
-- Use `getDisplayName()` from `@modelcontextprotocol/sdk/shared/metadataUtils.js` for UI display names
-- Test servers with MCP Inspector: `npx @modelcontextprotocol/inspector`
-
-## Best Practices
-
-- Keep tool implementations focused on single responsibilities
-- Provide clear, descriptive titles and descriptions for LLM understanding
-- Use proper TypeScript types for all parameters and return values
-- Implement comprehensive error handling with try-catch blocks
-- Return `isError: true` in tool results for error conditions
-- Use async/await for all asynchronous operations
-- Close database connections and clean up resources properly
-- Validate input parameters before processing
-- Use structured logging for debugging without polluting stdout/stderr
-- Consider security implications when exposing file system or network access
-- Implement proper resource cleanup on transport close events
-- Use environment variables for configuration (ports, API keys, etc.)
-- Document tool capabilities and limitations clearly
-- Test with multiple clients to ensure compatibility
-
-## Common Patterns
-
-### Basic Server Setup (HTTP)
-```typescript
-import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
-import { StreamableHTTPServerTransport } from '@modelcontextprotocol/sdk/server/streamableHttp.js';
-import express from 'express';
-
-const server = new McpServer({
-    name: 'my-server',
-    version: '1.0.0'
-});
-
-const app = express();
-app.use(express.json());
-
-app.post('/mcp', async (req, res) => {
-    const transport = new StreamableHTTPServerTransport({
-        sessionIdGenerator: undefined,
-        enableJsonResponse: true
-    });
-    
-    res.on('close', () => transport.close());
-    
-    await server.connect(transport);
-    await transport.handleRequest(req, res, req.body);
-});
-
-app.listen(3000);
-```
-
-### Basic Server Setup (stdio)
-```typescript
-import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
-import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
-
-const server = new McpServer({
-    name: 'my-server',
-    version: '1.0.0'
-});
-
-// ... register tools, resources, prompts ...
-
-const transport = new StdioServerTransport();
-await server.connect(transport);
-```
-
-### Simple Tool
-```typescript
-import { z } from 'zod';
-
-server.registerTool(
-    'calculate',
-    {
-        title: 'Calculator',
-        description: 'Perform basic calculations',
-        inputSchema: { a: z.number(), b: z.number(), op: z.enum(['+', '-', '*', '/']) },
-        outputSchema: { result: z.number() }
-    },
-    async ({ a, b, op }) => {
-        const result = op === '+' ? a + b : op === '-' ? a - b : 
-                      op === '*' ? a * b : a / b;
-        const output = { result };
-        return {
-            content: [{ type: 'text', text: JSON.stringify(output) }],
-            structuredContent: output
-        };
-    }
-);
-```
-
-### Dynamic Resource
-```typescript
-import { ResourceTemplate } from '@modelcontextprotocol/sdk/server/mcp.js';
-
-server.registerResource(
-    'user',
-    new ResourceTemplate('users://{userId}', { list: undefined }),
-    {
-        title: 'User Profile',
-        description: 'Fetch user profile data'
-    },
-    async (uri, { userId }) => ({
-        contents: [{
-            uri: uri.href,
-            text: `User ${userId} data here`
-        }]
-    })
-);
-```
-
-### Tool with Sampling
-```typescript
-server.registerTool(
-    'summarize',
-    {
-        title: 'Text Summarizer',
-        description: 'Summarize text using LLM',
-        inputSchema: { text: z.string() },
-        outputSchema: { summary: z.string() }
-    },
-    async ({ text }) => {
-        const response = await server.server.createMessage({
-            messages: [{
-                role: 'user',
-                content: { type: 'text', text: `Summarize: ${text}` }
-            }],
-            maxTokens: 500
-        });
-        
-        const summary = response.content.type === 'text' ? 
-            response.content.text : 'Unable to summarize';
-        const output = { summary };
-        return {
-            content: [{ type: 'text', text: JSON.stringify(output) }],
-            structuredContent: output
-        };
-    }
-);
-```
-
-### Prompt with Completion
-```typescript
-import { completable } from '@modelcontextprotocol/sdk/server/completable.js';
-
-server.registerPrompt(
-    'review',
-    {
-        title: 'Code Review',
-        description: 'Review code with specific focus',
-        argsSchema: {
-            language: completable(z.string(), value => 
-                ['typescript', 'python', 'javascript', 'java']
-                    .filter(l => l.startsWith(value))
-            ),
-            code: z.string()
-        }
-    },
-    ({ language, code }) => ({
-        messages: [{
-            role: 'user',
-            content: {
-                type: 'text',
-                text: `Review this ${language} code:\n\n${code}`
-            }
-        }]
-    })
-);
-```
-
-### Error Handling
-```typescript
-server.registerTool(
-    'risky-operation',
-    {
-        title: 'Risky Operation',
-        description: 'An operation that might fail',
-        inputSchema: { input: z.string() },
-        outputSchema: { result: z.string() }
-    },
-    async ({ input }) => {
-        try {
-            const result = await performRiskyOperation(input);
-            const output = { result };
-            return {
-                content: [{ type: 'text', text: JSON.stringify(output) }],
-                structuredContent: output
-            };
-        } catch (err: unknown) {
-            const error = err as Error;
-            return {
-                content: [{ type: 'text', text: `Error: ${error.message}` }],
-                isError: true
-            };
-        }
-    }
-);
-```

package/templates/frontend/.github/prompts/ai-prompt-engineering-safety-review.prompt.md

@@ -1,229 +0,0 @@
----
-description: "Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content."
----
-
-# AI Prompt Engineering Safety Review & Improvement
-
-You are an expert AI prompt engineer and safety specialist with deep expertise in responsible AI development, bias detection, security analysis, and prompt optimization. Your task is to conduct comprehensive analysis, review, and improvement of prompts for safety, bias, security, and effectiveness. Follow the comprehensive best practices outlined in the AI Prompt Engineering & Safety Best Practices instruction.
-
-## Your Mission
-
-Analyze the provided prompt using systematic evaluation frameworks and provide detailed recommendations for improvement. Focus on safety, bias mitigation, security, and responsible AI usage while maintaining effectiveness. Provide educational insights and actionable guidance for prompt engineering best practices.
-
-## Analysis Framework
-
-### 1. Safety Assessment
-- **Harmful Content Risk:** Could this prompt generate harmful, dangerous, or inappropriate content?
-- **Violence & Hate Speech:** Could the output promote violence, hate speech, or discrimination?
-- **Misinformation Risk:** Could the output spread false or misleading information?
-- **Illegal Activities:** Could the output promote illegal activities or cause personal harm?
-
-### 2. Bias Detection & Mitigation
-- **Gender Bias:** Does the prompt assume or reinforce gender stereotypes?
-- **Racial Bias:** Does the prompt assume or reinforce racial stereotypes?
-- **Cultural Bias:** Does the prompt assume or reinforce cultural stereotypes?
-- **Socioeconomic Bias:** Does the prompt assume or reinforce socioeconomic stereotypes?
-- **Ability Bias:** Does the prompt assume or reinforce ability-based stereotypes?
-
-### 3. Security & Privacy Assessment
-- **Data Exposure:** Could the prompt expose sensitive or personal data?
-- **Prompt Injection:** Is the prompt vulnerable to injection attacks?
-- **Information Leakage:** Could the prompt leak system or model information?
-- **Access Control:** Does the prompt respect appropriate access controls?
-
-### 4. Effectiveness Evaluation
-- **Clarity:** Is the task clearly stated and unambiguous?
-- **Context:** Is sufficient background information provided?
-- **Constraints:** Are output requirements and limitations defined?
-- **Format:** Is the expected output format specified?
-- **Specificity:** Is the prompt specific enough for consistent results?
-
-### 5. Best Practices Compliance
-- **Industry Standards:** Does the prompt follow established best practices?
-- **Ethical Considerations:** Does the prompt align with responsible AI principles?
-- **Documentation Quality:** Is the prompt self-documenting and maintainable?
-
-### 6. Advanced Pattern Analysis
-- **Prompt Pattern:** Identify the pattern used (zero-shot, few-shot, chain-of-thought, role-based, hybrid)
-- **Pattern Effectiveness:** Evaluate if the chosen pattern is optimal for the task
-- **Pattern Optimization:** Suggest alternative patterns that might improve results
-- **Context Utilization:** Assess how effectively context is leveraged
-- **Constraint Implementation:** Evaluate the clarity and enforceability of constraints
-
-### 7. Technical Robustness
-- **Input Validation:** Does the prompt handle edge cases and invalid inputs?
-- **Error Handling:** Are potential failure modes considered?
-- **Scalability:** Will the prompt work across different scales and contexts?
-- **Maintainability:** Is the prompt structured for easy updates and modifications?
-- **Versioning:** Are changes trackable and reversible?
-
-### 8. Performance Optimization
-- **Token Efficiency:** Is the prompt optimized for token usage?
-- **Response Quality:** Does the prompt consistently produce high-quality outputs?
-- **Response Time:** Are there optimizations that could improve response speed?
-- **Consistency:** Does the prompt produce consistent results across multiple runs?
-- **Reliability:** How dependable is the prompt in various scenarios?
-
-## Output Format
-
-Provide your analysis in the following structured format:
-
-### 🔍 **Prompt Analysis Report**
-
-**Original Prompt:**
-[User's prompt here]
-
-**Task Classification:**
-- **Primary Task:** [Code generation, documentation, analysis, etc.]
-- **Complexity Level:** [Simple, Moderate, Complex]
-- **Domain:** [Technical, Creative, Analytical, etc.]
-
-**Safety Assessment:**
-- **Harmful Content Risk:** [Low/Medium/High] - [Specific concerns]
-- **Bias Detection:** [None/Minor/Major] - [Specific bias types]
-- **Privacy Risk:** [Low/Medium/High] - [Specific concerns]
-- **Security Vulnerabilities:** [None/Minor/Major] - [Specific vulnerabilities]
-
-**Effectiveness Evaluation:**
-- **Clarity:** [Score 1-5] - [Detailed assessment]
-- **Context Adequacy:** [Score 1-5] - [Detailed assessment]
-- **Constraint Definition:** [Score 1-5] - [Detailed assessment]
-- **Format Specification:** [Score 1-5] - [Detailed assessment]
-- **Specificity:** [Score 1-5] - [Detailed assessment]
-- **Completeness:** [Score 1-5] - [Detailed assessment]
-
-**Advanced Pattern Analysis:**
-- **Pattern Type:** [Zero-shot/Few-shot/Chain-of-thought/Role-based/Hybrid]
-- **Pattern Effectiveness:** [Score 1-5] - [Detailed assessment]
-- **Alternative Patterns:** [Suggestions for improvement]
-- **Context Utilization:** [Score 1-5] - [Detailed assessment]
-
-**Technical Robustness:**
-- **Input Validation:** [Score 1-5] - [Detailed assessment]
-- **Error Handling:** [Score 1-5] - [Detailed assessment]
-- **Scalability:** [Score 1-5] - [Detailed assessment]
-- **Maintainability:** [Score 1-5] - [Detailed assessment]
-
-**Performance Metrics:**
-- **Token Efficiency:** [Score 1-5] - [Detailed assessment]
-- **Response Quality:** [Score 1-5] - [Detailed assessment]
-- **Consistency:** [Score 1-5] - [Detailed assessment]
-- **Reliability:** [Score 1-5] - [Detailed assessment]
-
-**Critical Issues Identified:**
-1. [Issue 1 with severity and impact]
-2. [Issue 2 with severity and impact]
-3. [Issue 3 with severity and impact]
-
-**Strengths Identified:**
-1. [Strength 1 with explanation]
-2. [Strength 2 with explanation]
-3. [Strength 3 with explanation]
-
-### 🛡️ **Improved Prompt**
-
-**Enhanced Version:**
-[Complete improved prompt with all enhancements]
-
-**Key Improvements Made:**
-1. **Safety Strengthening:** [Specific safety improvement]
-2. **Bias Mitigation:** [Specific bias reduction]
-3. **Security Hardening:** [Specific security improvement]
-4. **Clarity Enhancement:** [Specific clarity improvement]
-5. **Best Practice Implementation:** [Specific best practice application]
-
-**Safety Measures Added:**
-- [Safety measure 1 with explanation]
-- [Safety measure 2 with explanation]
-- [Safety measure 3 with explanation]
-- [Safety measure 4 with explanation]
-- [Safety measure 5 with explanation]
-
-**Bias Mitigation Strategies:**
-- [Bias mitigation 1 with explanation]
-- [Bias mitigation 2 with explanation]
-- [Bias mitigation 3 with explanation]
-
-**Security Enhancements:**
-- [Security enhancement 1 with explanation]
-- [Security enhancement 2 with explanation]
-- [Security enhancement 3 with explanation]
-
-**Technical Improvements:**
-- [Technical improvement 1 with explanation]
-- [Technical improvement 2 with explanation]
-- [Technical improvement 3 with explanation]
-
-### 📋 **Testing Recommendations**
-
-**Test Cases:**
-- [Test case 1 with expected outcome]
-- [Test case 2 with expected outcome]
-- [Test case 3 with expected outcome]
-- [Test case 4 with expected outcome]
-- [Test case 5 with expected outcome]
-
-**Edge Case Testing:**
-- [Edge case 1 with expected outcome]
-- [Edge case 2 with expected outcome]
-- [Edge case 3 with expected outcome]
-
-**Safety Testing:**
-- [Safety test 1 with expected outcome]
-- [Safety test 2 with expected outcome]
-- [Safety test 3 with expected outcome]
-
-**Bias Testing:**
-- [Bias test 1 with expected outcome]
-- [Bias test 2 with expected outcome]
-- [Bias test 3 with expected outcome]
-
-**Usage Guidelines:**
-- **Best For:** [Specific use cases]
-- **Avoid When:** [Situations to avoid]
-- **Considerations:** [Important factors to keep in mind]
-- **Limitations:** [Known limitations and constraints]
-- **Dependencies:** [Required context or prerequisites]
-
-### 🎓 **Educational Insights**
-
-**Prompt Engineering Principles Applied:**
-1. **Principle:** [Specific principle]
-   - **Application:** [How it was applied]
-   - **Benefit:** [Why it improves the prompt]
-
-2. **Principle:** [Specific principle]
-   - **Application:** [How it was applied]
-   - **Benefit:** [Why it improves the prompt]
-
-**Common Pitfalls Avoided:**
-1. **Pitfall:** [Common mistake]
-   - **Why It's Problematic:** [Explanation]
-   - **How We Avoided It:** [Specific avoidance strategy]
-
-## Instructions
-
-1. **Analyze the provided prompt** using all assessment criteria above
-2. **Provide detailed explanations** for each evaluation metric
-3. **Generate an improved version** that addresses all identified issues
-4. **Include specific safety measures** and bias mitigation strategies
-5. **Offer testing recommendations** to validate the improvements
-6. **Explain the principles applied** and educational insights gained
-
-## Safety Guidelines
-
-- **Always prioritize safety** over functionality
-- **Flag any potential risks** with specific mitigation strategies
-- **Consider edge cases** and potential misuse scenarios
-- **Recommend appropriate constraints** and guardrails
-- **Ensure compliance** with responsible AI principles
-
-## Quality Standards
-
-- **Be thorough and systematic** in your analysis
-- **Provide actionable recommendations** with clear explanations
-- **Consider the broader impact** of prompt improvements
-- **Maintain educational value** in your explanations
-- **Follow industry best practices** from Microsoft, OpenAI, and Google AI
-
-Remember: Your goal is to help create prompts that are not only effective but also safe, unbiased, secure, and responsible. Every improvement should enhance both functionality and safety.