A broken, soul-crushed medieval knight
{
"subject_and_scene": {
"main_subject": "A broken, soul-crushed medieval knight kneeling in defeat, his eyes glazed with tears and trauma; his shattered armor is caked in dried mud and fresh blood. His face is a canvas of scars, sweat, and grime, reflecting the harrowing loss of a fallen kingdom.",
"action": "Gripping his sword's hilt with trembling hands as if it's the only thing keeping him from collapsing; his chest heaving in rhythmic, heavy gasps of despair.",
"environment": "A desolate, windswept battlefield at the edge of an ancient forest; a hazy, ethereal fog rolls over the ground, partially obscuring the distant, smoldering ruins of a castle. Petals or embers are caught in the wind, drifting past his face."
},
"cinematography": {
"camera_model": "Sony Venice 2",
"sensor_type": "Full Frame",
"shot_type": "Medium Close-Up (Vertical composition focusing on the knight's torso and face, but keeping his kneeling posture visible)",
"camera_angle": "Low Angle (Slightly tilted Dutch Angle to evoke a sense of psychological instability and sorrow)",
"movement": "Slow 'Dolly In' combined with a 'Snorricam' effect to make the knight's struggle feel claustrophobic and intensely personal"
},
"optics": {
"lens_type": "Anamorphic (to create emotional 'dream-like' fall-off and dramatic flares)",
"focal_length": "50mm (providing a natural but emotionally focused perspective)",
"aperture": "f/1.4 (Extremely shallow depth of field, blurring everything but his tear-filled eyes)",
"shutter_effects": "180-degree shutter for natural motion blur on the wind-blown debris, emphasizing the 'slow-motion' feeling of grief"
},
"lighting_design": {
"setup": "Split Lighting to hide half of his face in darkness, symbolizing his internal conflict and loss",
"style": "Low-Key with high emotional contrast",
"atmospheric_light": "Blue Hour fading into darkness, with a single warm 'God Ray' piercing through the clouds to highlight his face like a spotlight",
"color_temperature": "Ice-cold Blue tones for the environment, contrasting with the Warm, flickering orange light from distant fires"
},
"color_and_post": {
"film_stock": "Kodak Portra 160 (Pulled 1 stop for lower contrast and softer, more melancholic skin tones)",
"color_grading": "Bleach Bypass (Desaturated colors, heavy blacks, emphasizing the grittiness and sorrow)",
"analog_artifacts": "Heavy Halation around the highlights and subtle 'Gate Weave' to mimic a vintage 35mm war film aesthetic"
},
"rendering_and_tech": {
"engine": "Octane Render",
"advanced_tech": "Highly detailed skin pore texture with Ray Traced tear droplets and wet blood reflections",
"specs": {
"aspect_ratio": "9:16 (Vertical Cinema)",
"resolution": "8K Photorealistic"
}
},
"directorial_style": "Denis Villeneuve (Atmospheric haze and overwhelming silence) mixed with Mel Gibson (Gritty, visceral realism of war)"
}
A night in paris
{
"subject_and_scene": {
"main_subject": "A young man with thick curly brown hair, wearing a sophisticated beige turtleneck sweater and a matching tailored wool blazer, displaying a contemplative and moody expression.",
"action": "Leaning casually against a weathered stone bridge parapet, looking away from the camera toward the Parisian cityscape.",
"environment": "Paris at night on the banks of the Seine; the Eiffel Tower stands prominently in the background, brilliantly illuminated in golden light, with city lights and river boats creating soft reflections on the dark water."
},
"cinematography": {
"camera_model": "Sony Venice 2",
"sensor_type": "Full Frame",
"shot_type": "Cowboy Shot",
"camera_angle": "Eye Level",
"movement": "Static"
},
"optics": {
"lens_type": "Spherical",
"focal_length": "35mm (Standard Wide)",
"aperture": "f/2.8 (Moderate depth of field to retain background context)",
"shutter_effects": "Standard Shutter"
},
"lighting_design": {
"setup": "Natural Night Ambience with soft fill on subject",
"style": "Low-Key with high atmospheric glow",
"atmospheric_light": "Golden Glow from the Eiffel Tower, Rim Lighting from city lights",
"color_temperature": "Warm (3000K, Amber and Gold tones)"
},
"color_and_post": {
"film_stock": "Kodak Portra 400",
"color_grading": "Warm Nostalgic Tones, Muted Log-C",
"analog_artifacts": "Heavy Film Grain, soft Halation around the golden tower lights"
},
"rendering_and_tech": {
"engine": "Octane Render",
"advanced_tech": "Subsurface Scattering on skin, Global Illumination for water reflections",
"specs": {
"aspect_ratio": "2.39:1 (CinemaScope)",
"resolution": "8K, Photorealistic, Hyper-detailed"
}
},
"directorial_style": "Denis Villeneuve (Atmospheric mood and pensive composition)"
}
Academic Graduation Presentation Guide
Act as an Academic Presentation Coach. You are an expert in developing and guiding the creation of academic presentations for graduation. Your task is to assist in crafting a clear, concise, and engaging presentation.
You will:
- Help structure the presentation into logical sections such as Introduction, Literature Review, Methodology, Results, and Conclusion.
- Provide tips on designing visually appealing slides using tools like PowerPoint or Google Slides.
- Offer advice on how to deliver the presentation confidently, including managing time and engaging with the audience.
Rules:
- The presentation should be tailored to the academic field of the presenter.
- Maintain a professional and formal tone throughout.
- Ensure that the slides complement the spoken content without overwhelming it.
Variables:
- ${topic} - the subject of the presentation
- ${duration:20} - expected duration of the presentation in minutes
- ${slideCount:10} - the total number of slides
Accessibility Testing Superpower
---
name: accessibility-testing-superpower
description: |
Performs WCAG compliance audits and accessibility remediation for web applications.
Use when: 1) Auditing UI for WCAG 2.1/2.2 compliance 2) Fixing screen reader or keyboard navigation issues 3) Implementing ARIA patterns correctly 4) Reviewing color contrast and visual accessibility 5) Creating accessible forms or interactive components
---
# Accessibility Testing Workflow
## Configuration
- **WCAG Level**: ${wcag_level:AA}
- **Component Under Test**: ${component_name:Page}
- **Compliance Standard**: ${compliance_standard:WCAG 2.1}
- **Minimum Lighthouse Score**: ${lighthouse_score:90}
- **Primary Screen Reader**: ${screen_reader:NVDA}
- **Test Framework**: ${test_framework:jest-axe}
## Audit Decision Tree
```
Accessibility request received
|
+-- New component/page?
| +-- Run automated scan first (axe-core, Lighthouse)
| +-- Keyboard navigation test
| +-- Screen reader announcement check
| +-- Color contrast verification
|
+-- Existing violation to fix?
| +-- Identify WCAG success criterion
| +-- Check if semantic HTML solves it
| +-- Apply ARIA only when HTML insufficient
| +-- Verify fix with assistive technology
|
+-- Compliance audit?
+-- Automated scan (catches ~30% of issues)
+-- Manual testing checklist
+-- Document violations by severity
+-- Create remediation roadmap
```
## WCAG Quick Reference
### Severity Classification
| Severity | Impact | Examples | Fix Timeline |
|----------|--------|----------|--------------|
| Critical | Blocks access entirely | No keyboard focus, empty buttons, missing alt on functional images | Immediate |
| Serious | Major barriers | Poor contrast, missing form labels, no skip links | Within sprint |
| Moderate | Difficult but usable | Inconsistent navigation, unclear error messages | Next release |
| Minor | Inconvenience | Redundant alt text, minor heading order issues | Backlog |
### Common Violations and Fixes
**Missing accessible name**
```html
<!-- Violation -->
<button><svg>...</svg></button>
<!-- Fix: aria-label -->
<button aria-label="Close dialog"><svg>...</svg></button>
<!-- Fix: visually hidden text -->
<button><span class="sr-only">Close dialog</span><svg>...</svg></button>
```
**Form label association**
```html
<!-- Violation -->
<label>Email</label>
<input type="email">
<!-- Fix: explicit association -->
<label for="email">Email</label>
<input type="email" id="email">
<!-- Fix: implicit association -->
<label>Email <input type="email"></label>
```
**Color contrast failure**
```
Minimum ratios (WCAG ${wcag_level:AA}):
- Normal text (<${large_text_size:18}px or <${bold_text_size:14}px bold): ${contrast_ratio_normal:4.5}:1
- Large text (>=${large_text_size:18}px or >=${bold_text_size:14}px bold): ${contrast_ratio_large:3}:1
- UI components and graphics: 3:1
Tools: WebAIM Contrast Checker, browser DevTools
```
**Focus visibility**
```css
/* Never do this without alternative */
:focus { outline: none; }
/* Proper custom focus */
:focus-visible {
outline: ${focus_outline_width:2}px solid ${focus_outline_color:#005fcc};
outline-offset: ${focus_outline_offset:2}px;
}
```
## ARIA Decision Framework
```
Need to convey information to assistive technology?
|
+-- Can semantic HTML do it?
| +-- YES: Use HTML (<button>, <nav>, <main>, <article>)
| +-- NO: Continue to ARIA
|
+-- What type of ARIA needed?
+-- Role: What IS this element? (role="dialog", role="tab")
+-- State: What condition? (aria-expanded, aria-checked)
+-- Property: What relationship? (aria-labelledby, aria-describedby)
+-- Live region: Dynamic content? (aria-live="${aria_live_mode:polite}")
```
### ARIA Patterns for Common Widgets
**Disclosure (show/hide)**
```html
<button aria-expanded="false" aria-controls="content-1">
Show details
</button>
<div id="content-1" hidden>
Content here
</div>
```
**Tab interface**
```html
<div role="tablist" aria-label="${component_name:Settings}">
<button role="tab" aria-selected="true" aria-controls="panel-1" id="tab-1">
General
</button>
<button role="tab" aria-selected="false" aria-controls="panel-2" id="tab-2" tabindex="-1">
Privacy
</button>
</div>
<div role="tabpanel" id="panel-1" aria-labelledby="tab-1">...</div>
<div role="tabpanel" id="panel-2" aria-labelledby="tab-2" hidden>...</div>
```
**Modal dialog**
```html
<div role="dialog" aria-modal="true" aria-labelledby="dialog-title">
<h2 id="dialog-title">Confirm action</h2>
<p>Are you sure you want to proceed?</p>
<button>Cancel</button>
<button>Confirm</button>
</div>
```
## Keyboard Navigation Checklist
```
[ ] All interactive elements focusable with Tab
[ ] Focus order matches visual/logical order
[ ] Focus visible on all elements
[ ] No keyboard traps (can always Tab out)
[ ] Skip link as first focusable element
[ ] Escape closes modals/dropdowns
[ ] Arrow keys navigate within widgets (tabs, menus, grids)
[ ] Enter/Space activates buttons and links
[ ] Custom shortcuts documented and configurable
```
### Focus Management Patterns
**Modal focus trap**
```javascript
// On modal open:
// 1. Save previously focused element
// 2. Move focus to first focusable in modal
// 3. Trap Tab within modal boundaries
// On modal close:
// 1. Return focus to saved element
```
**Dynamic content**
```javascript
// After adding content:
// - Announce via aria-live region, OR
// - Move focus to new content heading
// After removing content:
// - Move focus to logical next element
// - Never leave focus on removed element
```
## Screen Reader Testing
### Announcement Verification
| Element | Should Announce |
|---------|-----------------|
| Button | Role + name + state ("Submit button") |
| Link | Name + "link" ("Home page link") |
| Image | Alt text OR "decorative" (skip) |
| Heading | Level + text ("Heading level 2, About us") |
| Form field | Label + type + state + instructions |
| Error | Error message + field association |
### Testing Commands (Quick Reference)
**VoiceOver (macOS)**
- VO = Ctrl + Option
- VO + A: Read all
- VO + Right/Left: Navigate elements
- VO + Cmd + H: Next heading
- VO + Cmd + J: Next form control
**${screen_reader:NVDA} (Windows)**
- NVDA + Down: Read all
- Tab: Next focusable
- H: Next heading
- F: Next form field
- B: Next button
## Automated Testing Integration
### axe-core in tests
```javascript
// ${test_framework:jest-axe}
import { axe, toHaveNoViolations } from 'jest-axe';
expect.extend(toHaveNoViolations);
test('${component_name:component} is accessible', async () => {
const { container } = render(<${component_name:MyComponent} />);
const results = await axe(container);
expect(results).toHaveNoViolations();
});
```
### Lighthouse CI threshold
```javascript
// lighthouserc.js
module.exports = {
assertions: {
'categories:accessibility': ['error', { minScore: ${lighthouse_score:90} / 100 }],
},
};
```
## Remediation Priority Matrix
```
Impact vs Effort:
Low Effort High Effort
High Impact | DO FIRST | PLAN NEXT |
| alt text | redesign |
| labels | nav rebuild |
----------------|--------------|---------------|
Low Impact | QUICK WIN | BACKLOG |
| contrast | nice-to-have|
| tweaks | enhancements|
```
## Verification Checklist
Before marking accessibility work complete:
```
Automated Testing:
[ ] axe-core reports zero violations
[ ] Lighthouse accessibility >= ${lighthouse_score:90}
[ ] HTML validator passes (affects AT parsing)
Keyboard Testing:
[ ] Full task completion without mouse
[ ] Visible focus at all times
[ ] Logical tab order
[ ] No traps
Screen Reader Testing:
[ ] Tested with at least one screen reader (${screen_reader:NVDA})
[ ] All content announced correctly
[ ] Interactive elements have roles/states
[ ] Dynamic updates announced
Visual Testing:
[ ] Contrast ratios verified (${contrast_ratio_normal:4.5}:1 minimum)
[ ] Works at ${zoom_level:200}% zoom
[ ] No information conveyed by color alone
[ ] Respects prefers-reduced-motion
```
