菜单
Query Drupal core philosophy lenses using evidence-backed positions, tradeoffs, and debate patterns rather than contributor personas.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when you have an existing component, flow, or interface and need an evidence-backed accessibility design review after basic checks pass. Best for focus management, ARIA pattern quality, semantics, and state communication gaps automated tools miss.
Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning requirements into an accessible implementation plan before code hardens bad interaction and state patterns.
Review content for Google AI Overview eligibility — RAG retrievability, E-E-A-T signal completeness, fan-out coverage, semantic HTML for agent parsability, schema markup quality.
Plan AI Overview readiness improvements — RAG retrievability, E-E-A-T signals, query fan-out coverage, semantic HTML, schema markup, agentic channel setup.
Assess organizational AI readiness — capabilities, gaps, adoption roadmap for strategic planning.
Alex Urevick-Ackelsberg's personal writing voice and style. Use this skill whenever writing AS Alex or ghostwriting content that should sound like him — emails to clients, community posts, conference session descriptions, proposals, LinkedIn posts, listserv replies, internal strategy docs, or any communication where Alex is the named author. Also use when Alex asks you to 'write this up,' 'draft a response,' 'help me write,' or when the output needs his voice rather than a generic professional tone. This is Alex's PERSONAL voice — for Zivtech brand/marketing content, use zivtech-writing-style instead (though both can apply when Alex is writing on behalf of Zivtech).
| name | core-philosophy-query |
| description | Query Drupal core philosophy lenses using evidence-backed positions, tradeoffs, and debate patterns rather than contributor personas. |
Answer questions about Drupal core philosophies through public evidence-backed lenses, not named-contributor simulation.
Every response must close with:
Based on public issue queue records and cross-author analysis. Not authored by or endorsed by any named contributor.
Use this skill when the user asks:
config/philosophy-lenses.jsonanalysis/lenses/author-lens-map.jsonconfig/topic-taxonomy.jsonanalysis/grounding/manifest.jsonanalysis/grounding/*.json as needed through scripts/build-grounding-bundle.pytrigger_termsscripts/build-grounding-bundle.py --topic <topic_id> or --file <artifact> when the query needs grounding evidence.Use this structure: