persona-testing
Test LogiDocs Certify features from customer persona perspectives. Use when the user wants to test features as a customer, get simulated feedback, review UI from user perspective, or mentions "test as Aftrac", "test as Sirius", "customer feedback", "user testing", or "persona review".
Best use case
persona-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Test LogiDocs Certify features from customer persona perspectives. Use when the user wants to test features as a customer, get simulated feedback, review UI from user perspective, or mentions "test as Aftrac", "test as Sirius", "customer feedback", "user testing", or "persona review".
Test LogiDocs Certify features from customer persona perspectives. Use when the user wants to test features as a customer, get simulated feedback, review UI from user perspective, or mentions "test as Aftrac", "test as Sirius", "customer feedback", "user testing", or "persona review".
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "persona-testing" skill to help with this workflow task. Context: Test LogiDocs Certify features from customer persona perspectives. Use when the user wants to test features as a customer, get simulated feedback, review UI from user perspective, or mentions "test as Aftrac", "test as Sirius", "customer feedback", "user testing", or "persona review".
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/persona-testing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How persona-testing Compares
| Feature / Agent | persona-testing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Test LogiDocs Certify features from customer persona perspectives. Use when the user wants to test features as a customer, get simulated feedback, review UI from user perspective, or mentions "test as Aftrac", "test as Sirius", "customer feedback", "user testing", or "persona review".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Persona Testing Skill Test LogiDocs Certify from customer perspectives to identify UX issues, missing features, and friction points before actual customer feedback. ## When to Use Use this skill when: - Testing features from a customer perspective - Generating simulated customer feedback - Reviewing UI/UX from user viewpoint - Preparing for customer demos - Identifying friction points before release ## Available Personas ### Aftrac (End User) **Agent:** `aftrac-tester` **User:** Thabo Molefe - Quality & Compliance Manager **Context:** First-time compliance, CE/UKCA marking, ~50 components **Invoke:** "Test this feature as Aftrac" or "What would Thabo think of this?" ### Sirius (Consultant) **Agent:** `sirius-tester` **User:** Kate & Steve - Senior ISO Consultants **Context:** 1,200+ clients, ISO 9001/14001/45001 **Invoke:** "Review this as Sirius" or "Would Kate recommend this to clients?" ## Usage Patterns ### Feature Review ``` Review the documents page from Aftrac's perspective. ``` ### Browser Testing ``` As Sirius, test the signup flow and evaluate credibility. ``` ### Feedback Simulation ``` Generate feedback Aftrac would give after uploading 20 documents. ``` ## Testing Scenarios ### Aftrac Scenarios 1. **First Login** - First impression, can they understand what to do? 2. **Document Upload** - Upload and organize supplier certificates 3. **CE Marking Checklist** - Find and understand requirements 4. **Progress Report** - Answer CEO's "How close are we?" 5. **Expiring Certificate** - Handle upcoming expiry ### Sirius Scenarios 1. **Demo Evaluation** - Does it look credible for clients? 2. **Client Onboarding** - Set up new ISO 9001 client 3. **Evidence Search** - Find "management review process" evidence 4. **Multi-Client View** - Manage 15 active clients 5. **Audit Prep** - Prepare for ISO surveillance audit ## Comparison Matrix | Aspect | Aftrac | Sirius | |--------|--------|--------| | Role | End User | Consultant | | Expertise | Limited | Expert | | Need | Guidance | Efficiency | | Risk | Getting lost | Reputation damage | | UX Priority | Clarity | Speed | ## Post-Testing Report After testing, generate: ```markdown ## Persona Testing Report: [Feature] ### Tested As: [Persona] ### First Impressions - [What they notice immediately] ### Positive Observations - [What works well] ### Friction Points - [Where they struggle] ### Missing Features - [What they expected] ### Recommendations - [Priority fixes] ### Quote (In Character) > "[What they would actually say]" ``` ## Integration This skill works with the persona agents: - `.claude/agents/aftrac-tester.md` - `.claude/agents/sirius-tester.md` The agents contain detailed persona context, while this skill provides testing methodology.
Related Skills
testing-strategies
Design comprehensive testing strategies for software quality assurance. Use when planning test coverage, implementing test pyramids, or setting up testing infrastructure. Handles unit testing, integration testing, E2E testing, TDD, and testing best practices.
backend-testing
Write comprehensive backend tests including unit tests, integration tests, and API tests. Use when testing REST APIs, database operations, authentication flows, or business logic. Handles Jest, Pytest, Mocha, testing strategies, mocking, and test coverage.
wordpress-penetration-testing
This skill should be used when the user asks to "pentest WordPress sites", "scan WordPress for vulnerabilities", "enumerate WordPress users, themes, or plugins", "exploit WordPress vulnerabilities", or "use WPScan". It provides comprehensive WordPress security assessment methodologies.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
web-security-testing
Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.
unit-testing-test-generate
Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.
testing-qa
Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
ssh-penetration-testing
This skill should be used when the user asks to "pentest SSH services", "enumerate SSH configurations", "brute force SSH credentials", "exploit SSH vulnerabilities", "perform SSH tunneling", or "audit SSH security". It provides comprehensive SSH penetration testing methodologies and techniques.
sqlmap-database-pentesting
This skill should be used when the user asks to "automate SQL injection testing," "enumerate database structure," "extract database credentials using sqlmap," "dump tables and columns...
sqlmap-database-penetration-testing
This skill should be used when the user asks to "automate SQL injection testing," "enumerate database structure," "extract database credentials using sqlmap," "dump tables and columns from a vulnerable database," or "perform automated database penetration testing." It provides comprehensive guidance for using SQLMap to detect and exploit SQL injection vulnerabilities.
sql-injection-testing
This skill should be used when the user asks to "test for SQL injection vulnerabilities", "perform SQLi attacks", "bypass authentication using SQL injection", "extract database information through injection", "detect SQL injection flaws", or "exploit database query vulnerabilities". It provides comprehensive techniques for identifying, exploiting, and understanding SQL injection attack vectors across different database systems.