Results for “non-technical”

Design or revise Interpreter UI for non-developers with an ultra-minimal, utilitarian style inspired by the OpenAI website and ChatGPT, not the developer platform. Use when simplifying settings, onboarding, chat, forms, empty states, or helper copy; when removing extra containers, labels, or visual noise; when replacing technical wording with plain language; when clarifying hierarchy and making the main user action obvious; when making every visible label and status understandable to an average HR admin or other non-technical user; when hiding implementation details such as logs, IDs, endpoints, paths, or protocol names; or when a screen must respect the app's existing CSS variables and light/dark theme behavior.

The English summary is being prepared. Showing the original description.

Communicate data insights to non-technical stakeholders in a structured, persuasive format. Use when the user says "present these findings", "explain this analysis to leadership", "make a data presentation", "tell the story behind the data", "translate this into a business narrative", "make this insight actionable", "stakeholder readout", "executive summary of results", or needs to turn analysis output into a decision-ready document or slide deck.

The English summary is being prepared. Showing the original description.

Write, rewrite, review, and organize developer-facing documentation for web software projects. Use when creating or improving README files, docs homepages, quickstarts, tutorials, how-to guides, API/reference pages, conceptual explanations, migration guides, or troubleshooting content for frontend, backend, full-stack, SDK, API, or framework-based web products. This skill applies strong information architecture, task-first page structure, clear voice, runnable examples, version and prerequisite hygiene, accessibility rules, and docs-as-code maintenance habits. Do not use it for marketing copy, legal text, or non-technical customer-support articles.

The English summary is being prepared. Showing the original description.

Applies rigorous adversarial analysis to generate, critique, fix, and consolidate solutions for any problem (technical or non-technical). Use when facing complex problems requiring thorough analysis, multiple solution approaches, and validation of proposed fixes before implementation.

The English summary is being prepared. Showing the original description.

Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.

The English summary is being prepared. Showing the original description.

Use when the user adds a project to the workspace, opens an unfamiliar repo, asks "what is this project", "explain this codebase", or invokes explain-new-project. Explores a newly opened workspace project and writes a plain-language report for a self-taught, non-technical user—quick start (what it is + how to run) first, then optional depth—and always saves PROJECT_GUIDE.md in the project root.

The English summary is being prepared. Showing the original description.

Write an evergreen teaching longform for non-technical readers built from your own real material (systems you run, dated failures, numbers), structured as a stitched lesson that can live as a blog post, a GitHub guide hub and a newsletter issue. Use when turning lived engineering experience into a durable how-to. Triggers: /guide, make a guide, build a lesson, evergreen guide.

The English summary is being prepared. Showing the original description.

Explain a topic like I'm a 5 year old, as a single HTML artifact built from big pictures and very few words. Use this whenever the user asks for a dead-simple explanation of how something works, says "ELI5", "explain like I'm five", "簡単に説明して", "図で説明して", "初心者向けに", "素人にもわかるように", wants to explain a concept to a non-technical manager, customer, or family member, or asks for a visual explainer — even if they don't say "ELI5" explicitly.

The English summary is being prepared. Showing the original description.

Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger when users mention 'turn this into a course,' 'explain this codebase interactively,' 'teach this code,' 'interactive tutorial from code,' 'codebase walkthrough,' 'learn from this codebase,' or 'make a course from this project.' This skill produces a stunning, self-contained HTML file with scroll-based navigation, animated visualizations, embedded quizzes, and code-with-plain-English side-by-side translations.

The English summary is being prepared. Showing the original description.

Explain the same design observation to a designer, a developer, and a non-technical stakeholder. Same insight, three languages. Use when working cross-functionally or presenting design decisions to mixed audiences.

The English summary is being prepared. Showing the original description.

Design author-friendly content structures that work for non-technical content creators. Use when designing content structures for blocks in AEM Edge Delivery Services.

The English summary is being prepared. Showing the original description.

Protect your SaaS app from common vulnerabilities. Use when building auth, handling user data, or deploying features. Covers authentication, data protection, API security, and OWASP Top 10 for non-technical founders using AI tools.

The English summary is being prepared. Showing the original description.

Plain-English translation layer for non-technical Copilot CLI users. Translates every approval prompt, error message, and technical output into clear, jargon-free English with color-coded risk indicators.

The English summary is being prepared. Showing the original description.

Penetration test and red team report writing methodology. Covers executive summary structuring (risk-led narrative for non-technical readers), technical finding format (title, severity, affected scope, narrative, reproduction steps, impact, remediation, references), CVSS v3.1 / v4.0 scoring with vector justification, OWASP risk rating, evidence hygiene (redacting credentials, hashing client data, time-stamping every action), screenshot and PoC artifact management, finding chain narratives, scope/limitations/assumptions documentation, retest evidence and remediation tracking, deliverable formats (PDF, DOCX, HTML, JSON for SIEM ingestion), client-customer-deliverable separation, and common report mistakes (over-CVSSing, undermining the triager, missing the 'so what'). Use at the end of an engagement when authoring a deliverable, when restructuring a draft for executive readability, or when establishing a reusable report template for a consulting practice.

The English summary is being prepared. Showing the original description.