claude-code-arcane 1.0.0

package/skills/regulatory-affairs-head/scripts/regulatory_tracker.py

@@ -0,0 +1,199 @@
+#!/usr/bin/env python3
+"""
+Regulatory Submission Tracking System
+Automates monitoring and reporting of regulatory submission status
+"""
+
+import json
+import datetime
+from typing import Dict, List, Optional
+from dataclasses import dataclass, asdict
+from enum import Enum
+
+class SubmissionType(Enum):
+    FDA_510K = "FDA_510K"
+    FDA_PMA = "FDA_PMA"
+    FDA_DE_NOVO = "FDA_DE_NOVO"
+    EU_MDR_CE = "EU_MDR_CE"
+    ISO_CERTIFICATION = "ISO_CERTIFICATION"
+    GLOBAL_REGULATORY = "GLOBAL_REGULATORY"
+
+class SubmissionStatus(Enum):
+    PLANNING = "PLANNING"
+    IN_PREPARATION = "IN_PREPARATION"
+    SUBMITTED = "SUBMITTED"
+    UNDER_REVIEW = "UNDER_REVIEW"
+    ADDITIONAL_INFO_REQUESTED = "ADDITIONAL_INFO_REQUESTED"
+    APPROVED = "APPROVED"
+    REJECTED = "REJECTED"
+    WITHDRAWN = "WITHDRAWN"
+
+@dataclass
+class RegulatorySubmission:
+    submission_id: str
+    product_name: str
+    submission_type: SubmissionType
+    submission_status: SubmissionStatus
+    target_market: str
+    submission_date: Optional[datetime.date] = None
+    target_approval_date: Optional[datetime.date] = None
+    actual_approval_date: Optional[datetime.date] = None
+    regulatory_authority: str = ""
+    responsible_person: str = ""
+    notes: str = ""
+    last_updated: datetime.date = datetime.date.today()
+
+class RegulatoryTracker:
+    def __init__(self, data_file: str = "regulatory_submissions.json"):
+        self.data_file = data_file
+        self.submissions: Dict[str, RegulatorySubmission] = {}
+        self.load_data()
+    
+    def load_data(self):
+        """Load existing submission data from JSON file"""
+        try:
+            with open(self.data_file, 'r') as f:
+                data = json.load(f)
+                for sub_id, sub_data in data.items():
+                    # Convert date strings back to date objects
+                    for date_field in ['submission_date', 'target_approval_date', 
+                                     'actual_approval_date', 'last_updated']:
+                        if sub_data.get(date_field):
+                            sub_data[date_field] = datetime.datetime.strptime(
+                                sub_data[date_field], '%Y-%m-%d').date()
+                    
+                    # Convert enums
+                    sub_data['submission_type'] = SubmissionType(sub_data['submission_type'])
+                    sub_data['submission_status'] = SubmissionStatus(sub_data['submission_status'])
+                    
+                    self.submissions[sub_id] = RegulatorySubmission(**sub_data)
+        except FileNotFoundError:
+            print(f"No existing data file found. Starting fresh.")
+        except Exception as e:
+            print(f"Error loading data: {e}")
+    
+    def save_data(self):
+        """Save submission data to JSON file"""
+        data = {}
+        for sub_id, submission in self.submissions.items():
+            sub_dict = asdict(submission)
+            # Convert date objects to strings
+            for date_field in ['submission_date', 'target_approval_date', 
+                             'actual_approval_date', 'last_updated']:
+                if sub_dict.get(date_field):
+                    sub_dict[date_field] = sub_dict[date_field].strftime('%Y-%m-%d')
+            
+            # Convert enums to strings
+            sub_dict['submission_type'] = sub_dict['submission_type'].value
+            sub_dict['submission_status'] = sub_dict['submission_status'].value
+            
+            data[sub_id] = sub_dict
+        
+        with open(self.data_file, 'w') as f:
+            json.dump(data, f, indent=2)
+    
+    def add_submission(self, submission: RegulatorySubmission):
+        """Add new regulatory submission"""
+        self.submissions[submission.submission_id] = submission
+        self.save_data()
+        print(f"Added submission: {submission.submission_id}")
+    
+    def update_submission_status(self, submission_id: str, 
+                               new_status: SubmissionStatus, 
+                               notes: str = ""):
+        """Update submission status"""
+        if submission_id in self.submissions:
+            self.submissions[submission_id].submission_status = new_status
+            self.submissions[submission_id].notes = notes
+            self.submissions[submission_id].last_updated = datetime.date.today()
+            self.save_data()
+            print(f"Updated {submission_id} status to {new_status.value}")
+        else:
+            print(f"Submission {submission_id} not found")
+    
+    def get_submissions_by_status(self, status: SubmissionStatus) -> List[RegulatorySubmission]:
+        """Get all submissions with specific status"""
+        return [sub for sub in self.submissions.values() if sub.submission_status == status]
+    
+    def get_overdue_submissions(self) -> List[RegulatorySubmission]:
+        """Get submissions that are overdue"""
+        today = datetime.date.today()
+        overdue = []
+        for submission in self.submissions.values():
+            if (submission.target_approval_date and 
+                submission.target_approval_date < today and 
+                submission.submission_status not in [SubmissionStatus.APPROVED, 
+                                                   SubmissionStatus.REJECTED, 
+                                                   SubmissionStatus.WITHDRAWN]):
+                overdue.append(submission)
+        return overdue
+    
+    def generate_status_report(self) -> str:
+        """Generate comprehensive status report"""
+        report = []
+        report.append("REGULATORY SUBMISSION STATUS REPORT")
+        report.append("=" * 50)
+        report.append(f"Generated: {datetime.date.today()}")
+        report.append("")
+        
+        # Summary by status
+        status_counts = {}
+        for status in SubmissionStatus:
+            count = len(self.get_submissions_by_status(status))
+            if count > 0:
+                status_counts[status] = count
+        
+        report.append("SUBMISSION STATUS SUMMARY:")
+        for status, count in status_counts.items():
+            report.append(f"  {status.value}: {count}")
+        report.append("")
+        
+        # Overdue submissions
+        overdue = self.get_overdue_submissions()
+        if overdue:
+            report.append("OVERDUE SUBMISSIONS:")
+            for submission in overdue:
+                days_overdue = (datetime.date.today() - submission.target_approval_date).days
+                report.append(f"  {submission.submission_id} - {days_overdue} days overdue")
+            report.append("")
+        
+        # Active submissions requiring attention
+        active_statuses = [SubmissionStatus.SUBMITTED, SubmissionStatus.UNDER_REVIEW, 
+                          SubmissionStatus.ADDITIONAL_INFO_REQUESTED]
+        active_submissions = []
+        for status in active_statuses:
+            active_submissions.extend(self.get_submissions_by_status(status))
+        
+        if active_submissions:
+            report.append("ACTIVE SUBMISSIONS REQUIRING ATTENTION:")
+            for submission in active_submissions:
+                report.append(f"  {submission.submission_id} - {submission.product_name}")
+                report.append(f"    Status: {submission.submission_status.value}")
+                report.append(f"    Target Date: {submission.target_approval_date}")
+                report.append(f"    Authority: {submission.regulatory_authority}")
+                report.append("")
+        
+        return "\n".join(report)
+
+def main():
+    """Main function for command-line usage"""
+    tracker = RegulatoryTracker()
+    
+    # Generate and print status report
+    print(tracker.generate_status_report())
+    
+    # Example: Add a new submission
+    # new_submission = RegulatorySubmission(
+    #     submission_id="SUB-2024-001",
+    #     product_name="HealthTech Device X",
+    #     submission_type=SubmissionType.FDA_510K,
+    #     submission_status=SubmissionStatus.PLANNING,
+    #     target_market="United States",
+    #     target_approval_date=datetime.date(2024, 12, 31),
+    #     regulatory_authority="FDA",
+    #     responsible_person="John Doe"
+    # )
+    # tracker.add_submission(new_submission)
+
+if __name__ == "__main__":
+    main()

package/skills/release/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: release
+description: "Pre-release checklist and patch notes generation for web projects"
+category: "operations"
+argument-hint: "[checklist|patch-notes|both]"
+user-invocable: true
+allowed-tools: ["Read", "Bash", "Glob", "Grep", "Write"]
+---
+
+## Route
+
+| Argumento / Intención | Modo | Qué hace |
+|----------------------|------|----------|
+| `checklist` / "¿estamos listos para release?", "go/no-go" | CHECKLIST | Ejecuta Pre-Release Checklist completo |
+| `patch-notes` / "generar notas", "release notes", "changelog" | PATCH-NOTES | Genera patch notes desde git log / changelog.md |
+| `both` / (sin argumento) | BOTH | Checklist primero → patch notes al final |
+
+**Regla:** si hay blockers en CHECKLIST, reportarlos antes de proceder a PATCH-NOTES.
+
+## Checklist
+
+**Codebase Health** — Scan for `TODO`/`FIXME`/`HACK`. Report counts and locations. FIXMEs are potential blockers.
+
+**Build Verification**
+- [ ] Clean build succeeds (no warnings), reproducible from tag
+- [ ] Build version matches tagged commit
+- [ ] Environment configs verified per target (staging, production)
+- [ ] All env vars and secrets documented and set
+**Quality Gates**
+- [ ] Zero S1/S2 bugs (or documented exceptions with owner approval)
+- [ ] All critical-path features tested, no regressions
+- [ ] Performance budgets met (response times, memory, CPU)
+**Data and Infrastructure**
+- [ ] DB migrations tested forward and backward, rollback verified on staging
+- [ ] Cache invalidation strategy confirmed
+- [ ] API versioning and deprecation notices in place
+**Monitoring and Rollback**
+- [ ] Health checks and alerting configured
+- [ ] Crash/error reporting active, dashboard accessible
+- [ ] Rollback plan documented and tested
+- [ ] On-call schedule set for first 72 hours post-deploy
+**Compliance**
+- [ ] Third-party license attributions complete
+- [ ] Privacy policy and legal notices current
+- [ ] Analytics/telemetry verified and receiving data
+
+**Go / No-Go** — Summarize readiness, list blockers, require sign-offs from tech lead, QA, and product owner.
+
+---
+
+## Version Bump Criteria
+
+| Bump  | When                                                        |
+|-------|-------------------------------------------------------------|
+| Major | Breaking API changes, incompatible schema migrations, removed endpoints |
+| Minor | New features, new endpoints, backward-compatible additions  |
+| Patch | Bug fixes, performance improvements, dependency updates     |
+
+Default to the **higher** bump when uncertain.
+
+---
+
+## Patch Notes Generation
+
+**Data sources** (priority order):
+1. `production/releases/[version]/changelog.md` or `docs/CHANGELOG.md`
+2. `git log` between previous release tag and current tag/HEAD
+3. If none found: **BLOCKED** — instruct user to run `/changelog [version]` first.
+
+**Categories**: Features | Improvements | Fixes (grouped by area) | Breaking Changes
+
+**Writing rules**:
+- Describe user/consumer impact, not implementation details
+- Include before/after values for behavioral changes
+- Strip internal jargon, ticket numbers, and sprint references
+- Check for tone guide at `docs/PATCH-NOTES-STYLE.md` or project CLAUDE.md
+
+Present notes with change count per category. Ask before writing to `docs/patch-notes/[version].md`.
+
+---
+
+## Release Process
+
+1. **Tag** — annotated git tag from verified commit
+2. **Deploy** — staging first, smoke tests, then promote to production
+3. **Verify** — health checks, monitor error rates for 30 min
+4. **Communicate** — publish patch notes, notify stakeholders
+
+**Anti-patterns** (reject these): no rollback plan; skipping staging; undocumented breaking changes; missing migration rollback path; no monitoring before deploy; patch notes exposing internal system names or ticket IDs.

package/skills/release-announce/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: release-announce
+description: "Broadcast release announcement across Slack, Discord, Email, ClickUp, Jira with consistent changelog."
+category: "operations"
+argument-hint: "[version] [--channels slack,discord,email]"
+user-invocable: true
+allowed-tools: Read, Glob, Grep, Bash, Write
+---
+# Release Announcement Broadcaster
+
+Genera y distribuye release announcement en múltiples plataformas simultáneamente.
+
+## Flujo
+
+### 1. Gather release data
+
+Auto-gather: git log entre tags, merged PRs (`gh pr list`), closed tickets (Jira/ClickUp con release label), breaking changes (grep `BREAKING CHANGE`).
+
+### 2. Clasificar commits
+
+| Prefix | Sección |
+|--------|---------|
+| `feat:` | Features |
+| `fix:` | Bug Fixes |
+| `perf:` | Performance |
+| `refactor:` | Refactoring |
+| `docs:` | Documentation |
+| `test:` | Tests |
+| `chore:`, `ci:`, `build:` | Maintenance |
+| `BREAKING CHANGE` | Breaking Changes |
+
+### 3. Generar per-platform
+
+Core message consistente, adaptado:
+- **Slack:** Block Kit (header, sections mrkdwn, divider, context, action buttons)
+- **Discord:** Embed JSON (title, description, fields, color, footer)
+- **Email:** HTML (h1/h2/ul structure)
+- **ClickUp/Jira:** Markdown simple
+- **CHANGELOG.md:** Keep-a-changelog format con PR links
+
+### 4. Preview + Confirmation
+
+Mostrar preview por canal, pedir confirmación por plataforma (checkboxes).
+
+### 5. Distribute
+
+Ejecutar en paralelo con error handling. Si uno falla → continuar con resto → report success/failures.
+
+## Config
+
+`.claude/config/release.yml`: channels (slack targets+templates, discord webhook, email recipients+subject, clickup space_id, changelog path+format).
+
+## Comando
+
+`/release-announce [version] [--channels list]`. Sin version → detectar del tag más reciente. Channels overridea config.
+
+## Reglas
+
+- NO publicar sin confirmación final
+- Semver obligatorio: vMAJOR.MINOR.PATCH
+- Breaking changes siempre al top
+- Validar URLs antes de publicar
+- Idempotencia: re-run misma version → preguntar overwrite
+- Rollback plan: mencionar si aplica

package/skills/release-checklist/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: release-checklist
+description: "Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness."
+category: "operations"
+argument-hint: "[platform: pc|console|mobile|all]"
+user-invocable: true
+allowed-tools: Read, Glob, Grep, Write
+---
+
+> **Explicit invocation only**: Only run when user requests `/release-checklist`.
+
+## Phase 1: Parse Arguments
+
+Platform: `pc`, `console`, `mobile`, or `all` (default).
+
+## Phase 2: Load Context
+
+Read `CLAUDE.md` (project, version, platforms). Read current milestone from `production/milestones/`.
+
+## Phase 3: Scan Codebase
+
+Count TODO/FIXME/HACK comments with locations and severity. Check test results in output directories/CI logs.
+
+## Phase 4: Generate Checklist
+
+### Sections (all platforms)
+
+**Codebase Health:** TODO/FIXME/HACK counts (list top blockers).
+
+**Build Verification:** clean build all platforms, zero warnings, all assets loading, build size within budget, version number correct, reproducible from tagged commit.
+
+**Quality Gates:** zero S1/S2 bugs (or documented exceptions), critical paths QA signed off, performance budgets (FPS, memory, load times, no leaks), no regressions, soak test 4+ hours.
+
+**Content Complete:** no placeholder assets, all TODO/FIXME in content resolved, text proofread, localization-ready, audio mix finalized, credits complete.
+
+### Platform-specific
+
+**PC:** min/rec specs documented, KB+M controls, controller support (Xbox/PS/generic), resolution scaling (1080p-4K-ultrawide), windowed/borderless/fullscreen, graphics settings persist, Steam/Epic/GOG SDK, achievements, cloud saves, Steam Deck (if targeting).
+
+**Console:** TRC/TCR/Lotcheck, platform controller prompts, suspend/resume, user switching, connectivity loss handling, storage full handling, parental controls, platform achievements, certification submission.
+
+**Mobile:** App store guidelines, permissions justified, privacy policy, data safety labels, touch on multiple sizes, battery usage, background behavior, push notification permissions, IAP flow, app size limits.
+
+### Store / Distribution (all)
+
+Store metadata (descriptions, features, system reqs), screenshots per-platform, trailers, key art, age ratings (ESRB/PEGI), legal/EULA/privacy, license attributions, regional pricing.
+
+### Launch Readiness
+
+Analytics/telemetry verified, crash reporting configured, day-one patch (if needed), on-call 72h schedule, community announcements drafted, press/influencer keys, support team briefed, rollback plan documented.
+
+### Go / No-Go
+
+Rationale summary + blocking items + sign-offs required: QA Lead, Technical Director, Producer, Creative Director.
+
+## Phase 5: Save
+
+Present checklist + total items + known blockers. "May I write to `production/releases/release-checklist-[version].md`?"
+
+## Phase 6: Next Steps
+
+- `/gate-check` for formal phase gate verdict
+- Coordinate sign-offs via `/team-release`

package/skills/research-summarizer/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: research-summarizer
+description: "Structured research summarization: turns dense papers, articles, and reports into actionable briefs with key findings, comparative analyses, and properly formatted citations."
+argument-hint: ""
+category: "agile"
+user-invocable: true
+allowed-tools: Read, Glob, Grep, Bash
+---
+
+# Research Summarizer
+
+Structured research summarization workflow that turns dense source material into actionable briefs. Built for product managers, analysts, founders, and anyone who reads more than they should have to.
+
+## When This Skill Activates
+
+- "Summarize this paper / article / report"
+- "What are the key findings in this document?"
+- "Compare these sources"
+- "Extract citations from this PDF"
+- "Give me a research brief on [topic]"
+- Any request involving: summarize, research brief, literature review, citation, source comparison
+
+## Workflow
+
+### Single Source Summary
+
+1. **Identify source type**
+   - Academic paper: use IMRAD structure (Introduction, Methods, Results, Analysis, Discussion)
+   - Web article: use claim-evidence-implication structure
+   - Technical report: use executive summary structure
+   - Documentation: use reference summary structure
+
+2. **Extract structured brief**: Title, Author(s), Date, Source Type, Key Thesis, Key Findings (with evidence), Methodology, Limitations, Actionable Takeaways, Notable Quotes.
+
+3. **Assess quality**: Source credibility, evidence strength, recency, bias indicators.
+
+### Multi-Source Comparison
+
+1. Collect sources (2-5 documents)
+2. Summarize each using the single-source workflow
+3. Build comparison matrix (Central Thesis, Methodology, Key Finding, Sample/Scope, Credibility)
+4. Synthesize: convergent findings, divergent findings, gaps, weight of evidence
+5. Produce synthesis brief: Consensus Findings, Contested Points, Gaps, Recommendation
+
+### Citation Extraction
+
+1. Scan document for all references, footnotes, in-text citations
+2. Extract and format using requested style (APA 7 default)
+3. Classify: primary, secondary, tertiary sources
+4. Output sorted bibliography with classification tags
+
+Supported formats: **APA 7**, **IEEE**, **Chicago**, **Harvard**, **MLA 9**
+
+## Tooling
+
+### `scripts/extract_citations.py`
+
+```bash
+python3 scripts/extract_citations.py document.txt                       # APA default
+python3 scripts/extract_citations.py document.txt --format ieee         # IEEE format
+python3 scripts/extract_citations.py document.txt --format apa --output json  # JSON
+cat paper.txt | python3 scripts/extract_citations.py --stdin            # From stdin
+```
+
+### `scripts/format_summary.py`
+
+```bash
+python3 scripts/format_summary.py --template academic                   # Academic template
+python3 scripts/format_summary.py --template executive --length brief   # Brief executive
+python3 scripts/format_summary.py --list-templates                      # List all templates
+python3 scripts/format_summary.py --template article --output json      # JSON output
+```
+
+## Quality Assessment Framework
+
+| Dimension | High | Medium | Low |
+|-----------|------|--------|-----|
+| **Credibility** | Peer-reviewed, established author | Reputable outlet, known author | Blog, unknown author |
+| **Evidence** | Large sample, rigorous method | Moderate data, sound approach | Anecdotal, no data |
+| **Recency** | Within 2 years | 2-5 years old | 5+ years, may be outdated |
+| **Objectivity** | No conflicts, balanced view | Minor affiliations disclosed | Funded by interested party |
+
+**Overall**: 4 Highs = strong source; 2+ Mediums = adequate with caveats; 2+ Lows = verify independently.
+
+> See `references/summary-templates.md` for full template library and `references/citation-formats.md` for formatting rules.
+
+## Proactive Triggers
+
+- **Source has no date**: Note it. Undated sources lose credibility points.
+- **Source contradicts others**: Highlight the contradiction explicitly.
+- **Source behind paywall**: Note limited access. Suggest alternatives.
+- **Only one source for compare**: Ask for at least one more.
+- **Citations incomplete**: Flag missing fields. Don't invent metadata.
+- **Source 5+ years old in fast-moving field**: Warn about potential obsolescence.

package/skills/research-summarizer/references/citation-formats.md

@@ -0,0 +1,105 @@
+# Citation Formats Quick Reference
+
+## APA 7 (American Psychological Association)
+
+Default format for social sciences, business, and product research.
+
+### Journal Article
+Author, A. A., & Author, B. B. (Year). Title of article. *Title of Periodical*, *volume*(issue), page–page. https://doi.org/xxxxx
+
+**Example:**
+Smith, J., & Jones, K. (2023). Agile adoption in enterprise organizations. *Journal of Product Management*, *15*(2), 45–62. https://doi.org/10.1234/jpm.2023.001
+
+### Book
+Author, A. A. (Year). *Title of work: Capital letter also for subtitle*. Publisher.
+
+**Example:**
+Cagan, M. (2018). *Inspired: How to create tech products customers love*. Wiley.
+
+### Web Page
+Author, A. A. (Year, Month Day). *Title of page*. Site Name. URL
+
+**Example:**
+Torres, T. (2024, January 15). *Continuous discovery in practice*. Product Talk. https://www.producttalk.org/discovery
+
+### In-Text Citation
+- Parenthetical: (Smith & Jones, 2023)
+- Narrative: Smith and Jones (2023) found that...
+- 3+ authors: (Patel et al., 2022)
+
+---
+
+## IEEE (Institute of Electrical and Electronics Engineers)
+
+Standard for engineering, computer science, and technical research.
+
+### Format
+[N] A. Author, "Title of article," *Journal*, vol. X, no. Y, pp. Z–Z, Month Year, doi: 10.xxxx.
+
+### Journal Article
+[1] J. Smith and K. Jones, "Agile adoption in enterprise organizations," *J. Prod. Mgmt.*, vol. 15, no. 2, pp. 45–62, Mar. 2023, doi: 10.1234/jpm.2023.001.
+
+### Conference Paper
+[2] A. Patel, B. Chen, and C. Kumar, "Cross-functional team performance metrics," in *Proc. Int. Conf. Software Eng.*, 2022, pp. 112–119.
+
+### Book
+[3] M. Cagan, *Inspired: How to Create Tech Products Customers Love*. Hoboken, NJ, USA: Wiley, 2018.
+
+### In-Text Citation
+As shown in [1], agile adoption has increased...
+Multiple: [1], [3], [5]–[7]
+
+---
+
+## Chicago (Notes-Bibliography)
+
+Standard for humanities, history, and some business writing.
+
+### Footnote Format
+1. First Name Last Name, *Title of Book* (Place: Publisher, Year), page.
+2. First Name Last Name, "Title of Article," *Journal* Volume, no. Issue (Year): pages.
+
+### Bibliography Entry
+Last Name, First Name. *Title of Book*. Place: Publisher, Year.
+Last Name, First Name. "Title of Article." *Journal* Volume, no. Issue (Year): pages.
+
+---
+
+## Harvard
+
+Common in UK and Australian academic writing.
+
+### Format
+Author, A.A. (Year) *Title of book*. Edition. Place: Publisher.
+Author, A.A. (Year) 'Title of article', *Journal*, Volume(Issue), pp. X–Y.
+
+### In-Text Citation
+(Smith and Jones, 2023)
+Smith and Jones (2023) argue that...
+
+---
+
+## MLA 9 (Modern Language Association)
+
+Standard for arts and humanities.
+
+### Format
+Last, First. *Title of Book*. Publisher, Year.
+Last, First. "Title of Article." *Journal*, vol. X, no. Y, Year, pp. Z–Z.
+
+### In-Text Citation
+(Smith and Jones 45)
+Smith and Jones argue that "direct quote" (45).
+
+---
+
+## Quick Decision Guide
+
+| Field / Context | Recommended Format |
+|----------------|-------------------|
+| Social sciences, business, psychology | APA 7 |
+| Engineering, computer science, technical | IEEE |
+| Humanities, history, arts | Chicago or MLA |
+| UK/Australian academic | Harvard |
+| Internal business reports | APA 7 (most widely recognized) |
+| Product research briefs | APA 7 |