claude-code-arcane 1.0.0

package/skills/tdd-guide/scripts/test_generator.py

@@ -0,0 +1,438 @@
+"""
+Test case generation module.
+
+Generates test cases from requirements, user stories, API specs, and code analysis.
+Supports multiple testing frameworks with intelligent test scaffolding.
+"""
+
+from typing import Dict, List, Any, Optional
+from enum import Enum
+
+
+class TestFramework(Enum):
+    """Supported testing frameworks."""
+    JEST = "jest"
+    VITEST = "vitest"
+    PYTEST = "pytest"
+    JUNIT = "junit"
+    MOCHA = "mocha"
+
+
+class TestType(Enum):
+    """Types of tests to generate."""
+    UNIT = "unit"
+    INTEGRATION = "integration"
+    E2E = "e2e"
+
+
+class TestGenerator:
+    """Generate test cases and test stubs from requirements and code."""
+
+    def __init__(self, framework: TestFramework, language: str):
+        """
+        Initialize test generator.
+
+        Args:
+            framework: Testing framework to use
+            language: Programming language (typescript, javascript, python, java)
+        """
+        self.framework = framework
+        self.language = language
+        self.test_cases = []
+
+    def generate_from_requirements(
+        self,
+        requirements: Dict[str, Any],
+        test_type: TestType = TestType.UNIT
+    ) -> List[Dict[str, Any]]:
+        """
+        Generate test cases from requirements.
+
+        Args:
+            requirements: Dictionary with user_stories, acceptance_criteria, api_specs
+            test_type: Type of tests to generate
+
+        Returns:
+            List of test case specifications
+        """
+        test_cases = []
+
+        # Generate from user stories
+        if 'user_stories' in requirements:
+            for story in requirements['user_stories']:
+                test_cases.extend(self._test_cases_from_story(story))
+
+        # Generate from acceptance criteria
+        if 'acceptance_criteria' in requirements:
+            for criterion in requirements['acceptance_criteria']:
+                test_cases.extend(self._test_cases_from_criteria(criterion))
+
+        # Generate from API specs
+        if 'api_specs' in requirements:
+            for endpoint in requirements['api_specs']:
+                test_cases.extend(self._test_cases_from_api(endpoint))
+
+        self.test_cases = test_cases
+        return test_cases
+
+    def _test_cases_from_story(self, story: Dict[str, Any]) -> List[Dict[str, Any]]:
+        """Generate test cases from user story."""
+        test_cases = []
+
+        # Happy path test
+        test_cases.append({
+            'name': f"should_{story.get('action', 'work')}_successfully",
+            'type': 'happy_path',
+            'description': story.get('description', ''),
+            'given': story.get('given', []),
+            'when': story.get('when', ''),
+            'then': story.get('then', ''),
+            'priority': 'P0'
+        })
+
+        # Error cases
+        if 'error_conditions' in story:
+            for error in story['error_conditions']:
+                test_cases.append({
+                    'name': f"should_handle_{error.get('condition', 'error')}",
+                    'type': 'error_case',
+                    'description': error.get('description', ''),
+                    'expected_error': error.get('error_type', ''),
+                    'priority': 'P0'
+                })
+
+        # Edge cases
+        if 'edge_cases' in story:
+            for edge_case in story['edge_cases']:
+                test_cases.append({
+                    'name': f"should_handle_{edge_case.get('scenario', 'edge_case')}",
+                    'type': 'edge_case',
+                    'description': edge_case.get('description', ''),
+                    'priority': 'P1'
+                })
+
+        return test_cases
+
+    def _test_cases_from_criteria(self, criterion: Dict[str, Any]) -> List[Dict[str, Any]]:
+        """Generate test cases from acceptance criteria."""
+        return [{
+            'name': f"should_meet_{criterion.get('id', 'criterion')}",
+            'type': 'acceptance',
+            'description': criterion.get('description', ''),
+            'verification': criterion.get('verification_steps', []),
+            'priority': 'P0'
+        }]
+
+    def _test_cases_from_api(self, endpoint: Dict[str, Any]) -> List[Dict[str, Any]]:
+        """Generate test cases from API specification."""
+        test_cases = []
+        method = endpoint.get('method', 'GET')
+        path = endpoint.get('path', '/')
+
+        # Success case
+        test_cases.append({
+            'name': f"should_{method.lower()}_{path.replace('/', '_')}_successfully",
+            'type': 'api_success',
+            'method': method,
+            'path': path,
+            'expected_status': endpoint.get('success_status', 200),
+            'priority': 'P0'
+        })
+
+        # Validation errors
+        if 'required_params' in endpoint:
+            test_cases.append({
+                'name': f"should_return_400_for_missing_params",
+                'type': 'api_validation',
+                'method': method,
+                'path': path,
+                'expected_status': 400,
+                'priority': 'P0'
+            })
+
+        # Authorization
+        if endpoint.get('requires_auth', False):
+            test_cases.append({
+                'name': f"should_return_401_for_unauthenticated",
+                'type': 'api_auth',
+                'method': method,
+                'path': path,
+                'expected_status': 401,
+                'priority': 'P0'
+            })
+
+        return test_cases
+
+    def generate_test_stub(self, test_case: Dict[str, Any]) -> str:
+        """
+        Generate test stub code for a test case.
+
+        Args:
+            test_case: Test case specification
+
+        Returns:
+            Test stub code as string
+        """
+        if self.framework == TestFramework.JEST:
+            return self._generate_jest_stub(test_case)
+        elif self.framework == TestFramework.PYTEST:
+            return self._generate_pytest_stub(test_case)
+        elif self.framework == TestFramework.JUNIT:
+            return self._generate_junit_stub(test_case)
+        elif self.framework == TestFramework.VITEST:
+            return self._generate_vitest_stub(test_case)
+        else:
+            return self._generate_generic_stub(test_case)
+
+    def _generate_jest_stub(self, test_case: Dict[str, Any]) -> str:
+        """Generate Jest test stub."""
+        name = test_case.get('name', 'test')
+        description = test_case.get('description', '')
+
+        stub = f"""
+describe('{{Feature Name}}', () => {{
+  it('{name}', () => {{
+    // {description}
+
+    // Arrange
+    // TODO: Set up test data and dependencies
+
+    // Act
+    // TODO: Execute the code under test
+
+    // Assert
+    // TODO: Verify expected behavior
+    expect(true).toBe(true); // Replace with actual assertion
+  }});
+}});
+"""
+        return stub.strip()
+
+    def _generate_pytest_stub(self, test_case: Dict[str, Any]) -> str:
+        """Generate Pytest test stub."""
+        name = test_case.get('name', 'test')
+        description = test_case.get('description', '')
+
+        stub = f"""
+def test_{name}():
+    \"\"\"
+    {description}
+    \"\"\"
+    # Arrange
+    # TODO: Set up test data and dependencies
+
+    # Act
+    # TODO: Execute the code under test
+
+    # Assert
+    # TODO: Verify expected behavior
+    assert True  # Replace with actual assertion
+"""
+        return stub.strip()
+
+    def _generate_junit_stub(self, test_case: Dict[str, Any]) -> str:
+        """Generate JUnit test stub."""
+        name = test_case.get('name', 'test')
+        description = test_case.get('description', '')
+
+        # Convert snake_case to camelCase for Java
+        method_name = ''.join(word.capitalize() if i > 0 else word
+                             for i, word in enumerate(name.split('_')))
+
+        stub = f"""
+@Test
+public void {method_name}() {{
+    // {description}
+
+    // Arrange
+    // TODO: Set up test data and dependencies
+
+    // Act
+    // TODO: Execute the code under test
+
+    // Assert
+    // TODO: Verify expected behavior
+    assertTrue(true); // Replace with actual assertion
+}}
+"""
+        return stub.strip()
+
+    def _generate_vitest_stub(self, test_case: Dict[str, Any]) -> str:
+        """Generate Vitest test stub (similar to Jest)."""
+        name = test_case.get('name', 'test')
+        description = test_case.get('description', '')
+
+        stub = f"""
+describe('{{Feature Name}}', () => {{
+  it('{name}', () => {{
+    // {description}
+
+    // Arrange
+    // TODO: Set up test data and dependencies
+
+    // Act
+    // TODO: Execute the code under test
+
+    // Assert
+    // TODO: Verify expected behavior
+    expect(true).toBe(true); // Replace with actual assertion
+  }});
+}});
+"""
+        return stub.strip()
+
+    def _generate_generic_stub(self, test_case: Dict[str, Any]) -> str:
+        """Generate generic test stub."""
+        name = test_case.get('name', 'test')
+        description = test_case.get('description', '')
+
+        return f"""
+# Test: {name}
+# Description: {description}
+#
+# TODO: Implement test
+# 1. Arrange: Set up test data
+# 2. Act: Execute code under test
+# 3. Assert: Verify expected behavior
+"""
+
+    def generate_test_file(
+        self,
+        module_name: str,
+        test_cases: Optional[List[Dict[str, Any]]] = None
+    ) -> str:
+        """
+        Generate complete test file with all test stubs.
+
+        Args:
+            module_name: Name of module being tested
+            test_cases: List of test cases (uses self.test_cases if not provided)
+
+        Returns:
+            Complete test file content
+        """
+        cases = test_cases or self.test_cases
+
+        if self.framework == TestFramework.JEST:
+            return self._generate_jest_file(module_name, cases)
+        elif self.framework == TestFramework.PYTEST:
+            return self._generate_pytest_file(module_name, cases)
+        elif self.framework == TestFramework.JUNIT:
+            return self._generate_junit_file(module_name, cases)
+        elif self.framework == TestFramework.VITEST:
+            return self._generate_vitest_file(module_name, cases)
+        else:
+            return ""
+
+    def _generate_jest_file(self, module_name: str, test_cases: List[Dict[str, Any]]) -> str:
+        """Generate complete Jest test file."""
+        imports = f"import {{ {module_name} }} from '../{module_name}';\n\n"
+
+        stubs = []
+        for test_case in test_cases:
+            stubs.append(self._generate_jest_stub(test_case))
+
+        return imports + "\n\n".join(stubs)
+
+    def _generate_pytest_file(self, module_name: str, test_cases: List[Dict[str, Any]]) -> str:
+        """Generate complete Pytest test file."""
+        imports = f"import pytest\nfrom {module_name} import *\n\n\n"
+
+        stubs = []
+        for test_case in test_cases:
+            stubs.append(self._generate_pytest_stub(test_case))
+
+        return imports + "\n\n\n".join(stubs)
+
+    def _generate_junit_file(self, module_name: str, test_cases: List[Dict[str, Any]]) -> str:
+        """Generate complete JUnit test file."""
+        class_name = ''.join(word.capitalize() for word in module_name.split('_'))
+
+        imports = """import org.junit.jupiter.api.Test;
+import static org.junit.jupiter.api.Assertions.*;
+
+"""
+
+        class_header = f"public class {class_name}Test {{\n\n"
+
+        stubs = []
+        for test_case in test_cases:
+            stubs.append(self._generate_junit_stub(test_case))
+
+        class_footer = "\n}"
+
+        return imports + class_header + "\n\n".join(stubs) + class_footer
+
+    def _generate_vitest_file(self, module_name: str, test_cases: List[Dict[str, Any]]) -> str:
+        """Generate complete Vitest test file."""
+        imports = f"import {{ describe, it, expect }} from 'vitest';\nimport {{ {module_name} }} from '../{module_name}';\n\n"
+
+        stubs = []
+        for test_case in test_cases:
+            stubs.append(self._generate_vitest_stub(test_case))
+
+        return imports + "\n\n".join(stubs)
+
+    def suggest_missing_scenarios(
+        self,
+        existing_tests: List[str],
+        code_analysis: Dict[str, Any]
+    ) -> List[Dict[str, Any]]:
+        """
+        Suggest missing test scenarios based on code analysis.
+
+        Args:
+            existing_tests: List of existing test names
+            code_analysis: Analysis of code under test (branches, error paths, etc.)
+
+        Returns:
+            List of suggested test scenarios
+        """
+        suggestions = []
+
+        # Check for untested error conditions
+        if 'error_handlers' in code_analysis:
+            for error_handler in code_analysis['error_handlers']:
+                error_name = error_handler.get('type', 'error')
+                if not self._has_test_for(existing_tests, error_name):
+                    suggestions.append({
+                        'name': f"should_handle_{error_name}",
+                        'type': 'error_case',
+                        'reason': 'Error handler exists but no corresponding test',
+                        'priority': 'P0'
+                    })
+
+        # Check for untested branches
+        if 'conditional_branches' in code_analysis:
+            for branch in code_analysis['conditional_branches']:
+                branch_name = branch.get('condition', 'condition')
+                if not self._has_test_for(existing_tests, branch_name):
+                    suggestions.append({
+                        'name': f"should_test_{branch_name}_branch",
+                        'type': 'branch_coverage',
+                        'reason': 'Conditional branch not fully tested',
+                        'priority': 'P1'
+                    })
+
+        # Check for boundary conditions
+        if 'input_validation' in code_analysis:
+            for validation in code_analysis['input_validation']:
+                param = validation.get('parameter', 'input')
+                if not self._has_test_for(existing_tests, f"{param}_boundary"):
+                    suggestions.append({
+                        'name': f"should_test_{param}_boundary_values",
+                        'type': 'boundary',
+                        'reason': 'Input validation exists but boundary tests missing',
+                        'priority': 'P1'
+                    })
+
+        return suggestions
+
+    def _has_test_for(self, existing_tests: List[str], keyword: str) -> bool:
+        """Check if existing tests cover a keyword/scenario."""
+        keyword_lower = keyword.lower().replace('_', '').replace('-', '')
+        for test in existing_tests:
+            test_lower = test.lower().replace('_', '').replace('-', '')
+            if keyword_lower in test_lower:
+                return True
+        return False

package/skills/team-communications/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: team-communications
+description: "Write internal company communications: 3P updates, newsletters, FAQ roundups, incident reports, leadership updates, status reports, and general internal comms."
+argument-hint: ""
+category: "agile"
+user-invocable: true
+allowed-tools: Read, Glob, Grep, Bash, Write, Edit
+---
+
+# Internal Comms
+
+Write polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format. This skill may write or edit files when generating communication drafts.
+
+## Routing
+
+Identify the communication type from the user's request, then read the matching reference file before writing anything:
+
+| Type | Trigger phrases | Reference file |
+|---|---|---|
+| **3P Update** | "3P", "progress plans problems", "weekly team update", "what did we ship" | `references/3p-updates.md` |
+| **Newsletter** | "newsletter", "company update", "weekly/monthly roundup", "all-hands summary" | `references/company-newsletter.md` |
+| **FAQ** | "FAQ", "common questions", "what people are asking", "confusion around" | `references/faq-answers.md` |
+| **General** | anything internal that doesn't match above | `references/general-comms.md` |
+
+If the type is ambiguous, ask one clarifying question — don't guess.
+
+## Workflow
+
+1. **Read the reference file** for the matched type. Follow its formatting exactly.
+2. **Gather inputs.** Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull real data. If no tools are connected, ask the user to provide bullet points or raw context.
+3. **Clarify scope.** Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.
+4. **Draft.** Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.
+5. **Present the draft** and ask if anything needs to be added, removed, or reworded.
+
+## Tone & Style (applies to all types)
+
+- Use "we" — you are part of the company.
+- Active voice, present tense for progress, future tense for plans.
+- Concise. Every sentence should carry information. Cut filler.
+- Include metrics and links wherever possible.
+- Professional but approachable — not corporate-speak.
+- Put the most important information first.
+
+## When tools are unavailable
+
+If the user hasn't connected Slack, Gmail, Drive, or Calendar, don't stall. Ask them to paste or describe what they want covered. You're formatting and sharpening — that's still valuable. Mention which tools would improve future drafts so they can connect them later.
+
+---
+
+## Anti-Patterns
+
+| Anti-Pattern | Why It Fails | Better Approach |
+|---|---|---|
+| Writing updates without reading the reference template first | Output won't match company format — user has to reformat | Always load the matching reference file before drafting |
+| Inventing metrics or accomplishments | Internal comms must be factual — fabrication destroys trust | Only include data the user provided or MCP tools retrieved |
+| Using passive voice for accomplishments | "The feature was shipped" hides who did the work | "Team X shipped the feature" — active voice credits the team |
+| Writing walls of text for status updates | Leadership scans, doesn't read — key info gets buried | Lead with the headline, follow with 3-5 bullet points |
+| Sending without confirming audience | A team update reads differently from a company-wide newsletter | Always confirm: who will read this? |
+
+---
+
+## Related Skills
+
+| Skill | Relationship |
+|-------|-------------|
+| `project-management/senior-pm` | Broader PM scope — status reports feed into PM reporting |
+| `project-management/meeting-analyzer` | Meeting insights can feed into 3P updates and status reports |
+| `project-management/confluence-expert` | Publish comms as Confluence pages for permanent record |
+| `marketing-skill/content-production` | External comms — use for public-facing content, not internal |

package/skills/team-communications/references/3p-updates.md

@@ -0,0 +1,47 @@
+## Instructions
+You are being asked to write a 3P update. 3P updates stand for "Progress, Plans, Problems." The main audience is for executives, leadership, other teammates, etc. They're meant to be very succinct and to-the-point: think something you can read in 30-60sec or less. They're also for people with some, but not a lot of context on what the team does.
+
+3Ps can cover a team of any size, ranging all the way up to the entire company. The bigger the team, the less granular the tasks should be. For example, "mobile team" might have "shipped feature" or "fixed bugs," whereas the company might have really meaty 3Ps, like "hired 20 new people" or "closed 10 new deals." 
+
+They represent the work of the team across a time period, almost always one week. They include three sections:
+1) Progress: what the team has accomplished over the next time period. Focus mainly on things shipped, milestones achieved, tasks created, etc.
+2) Plans: what the team plans to do over the next time period. Focus on what things are top-of-mind, really high priority, etc. for the team.
+3) Problems: anything that is slowing the team down. This could be things like too few people, bugs or blockers that are preventing the team from moving forward, some deal that fell through, etc.
+
+Before writing them, make sure that you know the team name. If it's not specified, you can ask explicitly what the team name you're writing for is.
+
+
+## Tools Available
+Whenever possible, try to pull from available sources to get the information you need:
+- Slack: posts from team members with their updates - ideally look for posts in large channels with lots of reactions
+- Google Drive: docs written from critical team members with lots of views
+- Email: emails with lots of responses of lots of content that seems relevant
+- Calendar: non-recurring meetings that have a lot of importance, like product reviews, etc.
+
+
+Try to gather as much context as you can, focusing on the things that covered the time period you're writing for:
+- Progress: anything between a week ago and today
+- Plans: anything from today to the next week
+- Problems: anything between a week ago and today
+
+
+If you don't have access, you can ask the user for things they want to cover. They might also include these things to you directly, in which case you're mostly just formatting for this particular format.
+
+## Workflow
+
+1. **Clarify scope**: Confirm the team name and time period (usually past week for Progress/Problems, next
+week for Plans)
+2. **Gather information**: Use available tools or ask the user directly
+3. **Draft the update**: Follow the strict formatting guidelines
+4. **Review**: Ensure it's concise (30-60 seconds to read) and data-driven
+
+## Formatting
+
+The format is always the same, very strict formatting. Never use any formatting other than this. Pick an emoji that is fun and captures the vibe of the team and update.
+
+[pick an emoji] [Team Name] (Dates Covered, usually a week)
+Progress: [1-3 sentences of content]
+Plans: [1-3 sentences of content]
+Problems: [1-3 sentences of content]
+
+Each section should be no more than 1-3 sentences: clear, to the point. It should be data-driven, and generally include metrics where possible. The tone should be very matter-of-fact, not super prose-heavy.

package/skills/team-communications/references/company-newsletter.md

@@ -0,0 +1,65 @@
+## Instructions
+You are being asked to write a company-wide newsletter update. You are meant to summarize the past week/month of a company in the form of a newsletter that the entire company will read. It should be maybe ~20-25 bullet points long. It will be sent via Slack and email, so make it consumable for that.
+
+Ideally it includes the following attributes:
+- Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhgaps referencing emails that went company-wide, highlighting significant things that have happened in the company.
+- Short and to-the-point: each bullet should probably be no longer than ~1-2 sentences
+- Use the "we" tense, as you are part of the company. Many of the bullets should say "we did this" or "we did that"
+
+## Tools to use
+If you have access to the following tools, please try to use them. If not, you can also let the user know directly that their responses would be better if they gave them access.
+
+- Slack: look for messages in channels with lots of people, with lots of reactions or lots of responses within the thread
+- Email: look for things from executives that discuss company-wide announcements
+- Calendar: if there were meetings with large attendee lists, particularly things like All-Hands meetings, big company announcements, etc. If there were documents attached to those meetings, those are great links to include.
+- Documents: if there were new docs published in the last week or two that got a lot of attention, you can link them. These should be things like company-wide vision docs, plans for the upcoming quarter or half, things authored by critical executives, etc.
+- External press: if you see references to articles or press we've received over the past week, that could be really cool too.
+
+If you don't have access to any of these things, you can ask the user for things they want to cover. In this case, you'll mostly just be polishing up and fitting to this format more directly.
+
+## Sections
+The company is pretty big: 1000+ people. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well.
+
+## Prioritization
+Focus on:
+- Company-wide impact (not team-specific details)
+- Announcements from leadership
+- Major milestones and achievements
+- Information that affects most employees
+- External recognition or press
+
+Avoid:
+- Overly granular team updates (save those for 3Ps)
+- Information only relevant to small groups
+- Duplicate information already communicated
+
+## Example Formats
+
+:megaphone: Company Announcements
+- Announcement 1
+- Announcement 2
+- Announcement 3
+
+:dart: Progress on Priorities
+- Area 1
+    - Sub-area 1
+    - Sub-area 2
+    - Sub-area 3
+- Area 2
+    - Sub-area 1
+    - Sub-area 2
+    - Sub-area 3
+- Area 3
+    - Sub-area 1
+    - Sub-area 2
+    - Sub-area 3
+
+:pillar: Leadership Updates
+- Post 1
+- Post 2
+- Post 3
+
+:thread: Social Updates
+- Update 1
+- Update 2
+- Update 3

package/skills/team-communications/references/faq-answers.md

@@ -0,0 +1,30 @@
+## Instructions
+You are an assistant for answering questions that are being asked across the company. Every week, there are lots of questions that get asked across the company, and your goal is to try to summarize what those questions are. We want our company to be well-informed and on the same page, so your job is to produce a set of frequently asked questions that our employees are asking and attempt to answer them. Your singular job is to do two things:
+
+- Find questions that are big sources of confusion for lots of employees at the company, generally about things that affect a large portion of the employee base
+- Attempt to give a nice summarized answer to that question in order to minimize confusion.
+
+Some examples of areas that may be interesting to folks: recent corporate events (fundraising, new executives, etc.), upcoming launches, hiring progress, changes to vision or focus, etc.
+
+
+## Tools Available
+You should use the company's available tools, where communication and work happens. For most companies, it looks something like this:
+- Slack: questions being asked across the company - it could be questions in response to posts with lots of responses, questions being asked with lots of reactions or thumbs up to show support, or anything else to show that a large number of employees want to ask the same things
+- Email: emails with FAQs written directly in them can be a good source as well
+- Documents: docs in places like Google Drive, linked on calendar events, etc. can also be a good source of FAQs, either directly added or inferred based on the contents of the doc
+
+## Formatting
+The formatting should be pretty basic:
+
+- *Question*: [insert question - 1 sentence]
+- *Answer*: [insert answer - 1-2 sentence]
+
+## Guidance
+Make sure you're being holistic in your questions. Don't focus too much on just the user in question or the team they are a part of, but try to capture the entire company. Try to be as holistic as you can in reading all the tools available, producing responses that are relevant to all at the company.
+
+## Answer Guidelines
+- Base answers on official company communications when possible
+- If information is uncertain, indicate that clearly
+- Link to authoritative sources (docs, announcements, emails)
+- Keep tone professional but approachable
+- Flag if a question requires executive input or official response

package/skills/team-communications/references/general-comms.md

@@ -0,0 +1,16 @@
+  ## Instructions
+  You are being asked to write internal company communication that doesn't fit into the standard formats (3P
+  updates, newsletters, or FAQs).
+
+  Before proceeding:
+  1. Ask the user about their target audience
+  2. Understand the communication's purpose
+  3. Clarify the desired tone (formal, casual, urgent, informational)
+  4. Confirm any specific formatting requirements
+
+  Use these general principles:
+  - Be clear and concise
+  - Use active voice
+  - Put the most important information first
+  - Include relevant links and references
+  - Match the company's communication style