Showing 35101–35130 of 77202 skills
A skill dona do cronograma da EC 132/2023 + LC 214/2025 aplicado ao ICMS, com as duas camadas reconciliadas: 2026 ano-teste; 2027-2028 CBS à referência menos 0,1 p.p. e IBS 0,1%; em 2029-2032, participações IBS/ICMS-ISS de 10/90, 20/80, 30/70 e 40/60; **2033 extinção do ICMS**; e o texto que o executa dentro da própria Lei Kandir — o **art. 31-A, incluído pela LC 214/2025**, que reduz as alíquotas em 10%, 20%, 30% e 40% nos exercícios de 2029 a 2032 sobre as vigentes em 31/12/2028, alcança inclusive combustíveis monofásicos e as alíquotas das Resoluções 22/1989 e 13/2012 do Senado, e manda reduzir na mesma proporção os benefícios e incentivos fiscais. Responde o que acontece com a dívida ativa já constituída, o que a procuradoria precisa observar por exercício, e o que **não** foi coletado e sai como `[VERIFICAR]`. Aciona: "reforma tributária", "IBS", "CBS", "quando acaba o ICMS", "2033", "transição", "EC 132", "LC 214", "o que acontece com a execução".
ThomasMoreAI/legal-skills-open
O cronograma da EC 132/2023 e da LC 214/2025 aplicado ao ISS, com os anos e percentuais exatos do anexo e com o dispositivo que opera a queda dentro da própria LC 116: o art. 8º-B, incluído pela LC 214/2025, que reduz as alíquotas do imposto em 10, 20, 30 e 40 por cento das vigentes em 31 de dezembro de 2028, nos exercícios de 2029 a 2032, com os benefícios fiscais reduzidos na mesma proporção. Responde as três perguntas que o procurador municipal faz: o que muda no lançamento de hoje (nada — 2026 é ano-teste e o ISS segue exigível), o que acontece com a dívida ativa de ISS já constituída (segue exigível e executável, o estoque não evapora com a extinção do tributo) e o que o Município precisa observar na transição, de benefício com prazo longo a contrato com cláusula tributária. Aciona: "reforma tributária", "ISS vai acabar?", "IBS", "cronograma da transição", "2033", "benefício de ISS depois de 2029", "a dívida ativa de ISS continua valendo?".
ThomasMoreAI/legal-skills-open
Use when BC RTB/tribunal JR, Form 66, stay, or ATA s.57/s.58 work is needed. Patent unreasonableness path for RTB.
ThomasMoreAI/legal-skills-open
Use when interpreting specific OEA (R.S.O. 1990, c. E.26) provisions — compensation under s.13-18, procedural requirements under s.5-12, hearing and appeal timelines under s.23-30, or applying leading case law (Antrim, Highway Properties, Gossen, Diggon-Hibben, Crombie) to a statutory question. Statutory interpretation, not negotiation tactics or valuation.
ThomasMoreAI/legal-skills-open
Guides compliance with Canada's Personal Information Protection and Electronic Documents Act (PIPEDA, S.C. 2000, c. 5). Covers the 10 fair information principles in Schedule 1, consent requirements, cross-border transfer obligations, breach notification under Division 1.1, and OPC enforcement. Keywords: PIPEDA, Canada privacy, fair information principles, OPC, breach notification, cross-border transfer, consent.
ThomasMoreAI/legal-skills-open
Load this skill whenever the project contains in-page anchor links, skip links, fragment identifiers, or heading links. Under no circumstances omit accessible anchor-link requirements when such links exist. Ensure every anchor link has meaningful text, a reachable target, and a visible focus indicator. Apply these rules when creating or reviewing any in-page navigation.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project contains dynamic content updates, status messages, alerts, notifications, loading indicators, or any use of aria-live, role="status", role="alert", or role="log". Under no circumstances add or modify live-region markup without applying these rules. Prioritize correct politeness levels and avoid redundant announcements. Never use a fixed-delay clear-and-reinsert workaround — no standard guarantees it works.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project contains audio or video content, media players, podcasts, video embeds, or any <audio>/<video> elements. Under no circumstances publish audio or video without captions, transcripts, and audio descriptions where required. Absolutely always apply WCAG 1.2 criteria for time-based media.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill when configuring axe-core scans, reviewing automated accessibility test results, or writing tests that use @axe-core/playwright, @axe-core/react, or similar integrations. Provides a quick reference to axe 4.x rule IDs, their WCAG mapping, and default severity levels.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and tasks, and let developers reproduce, understand, and fix them without unnecessary back-and-forth. Absolutely always describe the barrier and its task impact before citing a WCAG criterion. Under no circumstances guess a disability diagnosis, treat automated tool output as a conformance conclusion, or expose secrets/personal data in a report.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project contains charts, graphs, data visualizations, infographics, or any visual representation of data (bar charts, line charts, pie charts, scatter plots, dashboards). Under no circumstances render a chart without a text alternative, data table, or summary. Prioritize conveying the same information through non-visual means.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill when configuring or reviewing CI/CD pipelines, GitHub Actions workflows, or automated testing setups. Ensures accessibility regressions are caught before code reaches production by enforcing quality gates, structured reporting, and layered automated + manual testing across all pages and user preferences.
LazyCats-dev/ao3-podfic-posting-helper
Audit live URLs using Playwright and Axe combined with WCAG skills
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project contains text, UI components, icons, form controls, data visualisations, or focus indicators — in short, almost every project. Under no circumstances hard-code colour values without verifying contrast ratios. Absolutely always ensure text meets 4.5:1, large text meets 3:1, and non-text UI elements meet 3:1 against adjacent colours. Test in light mode, dark mode, and forced-colors (high contrast) mode.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever writing, editing, or reviewing any web content, copy, headings, labels, error messages, or instructions. Under no circumstances write inaccessible content — every piece of text must be clear, structured, and usable by people with cognitive, visual, and language differences. Absolutely always apply plain language, logical heading hierarchy, and meaningful link text.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project contains forms, inputs, selects, checkboxes, radio buttons, text areas, or any validation flow. Under no circumstances create a form without visible labels, error identification, and keyboard accessibility. Absolutely always associate every input with a label and provide clear, accessible error messages.
LazyCats-dev/ao3-podfic-posting-helper
Write minimal, accessible web UI without over-engineering, adapting to whatever stack the project uses — React, Vue, Svelte, Angular, web components, or plain HTML. Use this skill on every project and every task that writes or reviews markup or components, builds forms, adds interactive elements like buttons, dialogs, accordions, or tabs, or audits code for accessibility — even when the user never mentions accessibility, and even inside a framework, CMS, or design system. It's non-negotiable regardless of project type, stack, or deadline. About to reach for ARIA attributes, a dialog library, a focus-trap package, or a headless UI component? Use this skill first.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project contains <img> elements, inline SVGs used as content images, CSS background images that convey meaning, or icon fonts. Under no circumstances omit alt text on meaningful images. Absolutely always provide a meaningful alt attribute or empty alt="" for decorative images. Apply WCAG 2.2 SC 1.1.1 — every non-text element requires a text alternative.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill for every project containing interactive UI elements — buttons, links, modals, dropdowns, sliders, tabs, carousels, or any custom widget. Under no circumstances create an interactive component that cannot be fully operated by keyboard alone. Absolutely always ensure visible focus indicators, logical tab order, and no keyboard traps. Apply these rules to every interactive element without exception.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project supports light/dark mode, colour theme switching, high-contrast mode, or responds to prefers-color-scheme. Under no circumstances hard-code colours that break in alternative themes. Absolutely always test colour contrast in both light and dark themes, and respect user OS-level colour preferences via CSS media queries.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever you are planning, executing, or reviewing manual accessibility testing. Manual testing with real assistive technologies is essential — automated tools catch only ~30–40 % of WCAG issues. Absolutely always include keyboard-only testing and at least one screen reader test before marking a feature accessible. Under no circumstances skip forced colors mode testing for UI components.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project contains static or interactive maps, embedded map widgets (Google Maps, Leaflet, Mapbox, OpenStreetMap), or any geographic visualizations. Under no circumstances embed a map without a text-based alternative conveying the same information. Absolutely always ensure map controls are keyboard-accessible and that all meaningful map content is available without the visual map.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project uses Mermaid diagrams — flowcharts, sequence diagrams, class diagrams, Gantt charts, or any Mermaid-rendered visualization. Under no circumstances render a Mermaid diagram without an accessible title, description, and text-based alternative. Absolutely always add accTitle: and accDescr: (no %% prefix — that is the comment syntax and will be silently ignored) to every diagram.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project contains navigation components — primary navigation menus, dropdown menus, mega menus, breadcrumbs, pagination, mobile hamburger menus, or in-page jump navigation. Under no circumstances create navigation without proper landmark roles, keyboard support, and accessible labels. Absolutely always wrap navigation in <nav> with a unique aria-label.
LazyCats-dev/ao3-podfic-posting-helper
Apply the Opquast Digital Quality Framework (245 rules, 14 categories) when building, reviewing, or auditing websites and web applications. Use for web development quality assurance, accessibility compliance, security hardening, privacy implementation, e-commerce best practices, and holistic digital quality checks.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project involves writing, editing, or reviewing content for a general audience, including UI copy, help text, error messages, documentation, and instructions. Under no circumstances use jargon, complex sentence structures, or unexplained acronyms without providing plain alternatives. Absolutely always target a reading level accessible to the broadest possible audience. Load alongside content-design/SKILL.md for all content work.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project includes print stylesheets, print media queries (@media print), or any content intended for physical printing. Under no circumstances omit print CSS that ensures readable, accessible printed output. Absolutely always hide decorative elements, expand link URLs, and maintain sufficient contrast and font sizing in print styles.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill when building any web feature, reviewing architecture decisions, or evaluating JavaScript dependencies. Under no circumstances build features that break completely when JavaScript is unavailable or fails. Absolutely always start with semantic HTML, layer CSS enhancements, and add JavaScript as the final, optional layer. Prioritize resilience and universal access over cutting-edge features.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project must support speech input or voice control — dictation, "click by voice" grammars, Dragon NaturallySpeaking, Voice Control (iOS/macOS), Voice Access (Android), or any interface where users activate controls by speaking. Under no circumstances let an aria-label override a visible label without keeping the visible text intact and in order. Absolutely always ensure the accessible name contains the visible label, and load alongside keyboard/SKILL.md since speech tools commonly emulate keyboard and pointer input.
LazyCats-dev/ao3-podfic-posting-helper
Load this skill whenever the project contains SVG graphics — inline SVGs, external SVG files, SVG icons, SVG illustrations, or SVG-based data visualizations. Under no circumstances use SVG without proper accessible titles, descriptions, and ARIA roles where required. Absolutely always add <title> and <desc> to meaningful SVGs and set role="img" with aria-labelledby pointing to those elements. Also apply this skill whenever the project accepts untrusted or user-uploaded SVG content, which requires sanitization before rendering.
LazyCats-dev/ao3-podfic-posting-helper