A

Knowledge Pack Files

AICTPO AI Coding Agents Skill Pack Files

Browse the source files that power the AICTPO AI Coding Agents MCP server knowledge pack.

Available free v0.2.0 Browser
$ sidebutton install aictpo
Download ZIP
faq/_skill.md
2.1 KB

FAQ

Accordion section with 9 questions about the AI agents platform. The section anchors at #faq on the home page rather than living at its own URL.

Layout

The section heading appears above a vertical stack of 9 question rows. Each row collapses to a single line by default and expands inline when its trigger button is clicked. Rows are not mutually exclusive — the user can have several open simultaneously.

Interaction

Each question row is a button with aria-expanded toggling between "false" (collapsed) and "true" (expanded). The answer panel is the next sibling and is hidden via [hidden] or zero-height styling when collapsed. Clicking the button or pressing Enter / Space while focused toggles the state.

Selectors

ElementSelector
Section rootsection#faq, [data-section="faq"]
Question buttonbutton[aria-expanded] (within the section)
Question labelthe button's text content
Answer panelelement referenced by aria-controls
Active (open) statebutton[aria-expanded="true"]

Common tasks

Snapshot all questions: scroll #faq into view, list every button[aria-expanded] inside it, capture text content for each.

Read all answers: for each question button, click to expand if aria-expanded="false", snapshot the matching answer panel by aria-controls ID, then collapse.

Verify count and order: assert exactly 9 question rows and that the visible label text matches the expected question copy.

Gotchas

  • The answer panels are inert when collapsed — they may not be in the accessibility tree at all, so a snapshot before expansion will miss them.
  • Smooth-scroll on the parent page can intercept #faq deep links; wait for scroll to settle before reading positions.
  • The accordion is intentionally non-exclusive. Tests that assume "expanding question N collapses question N-1" will fail.
  • Keyboard activation works on Enter and Space — both should be supported in any QA flow that exercises a11y.