Skip to content
Back to skills

Extension Lifecycle

ASecurity

`enable()` and `disable()` must be adjacent in `extension.js`.

  • 14 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 19, 2026
toolsgo

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add itsnin/spotlight --skill extension-lifecycle --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Extension Lifecycle?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Extension Lifecycle
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/itsnin-extension-lifecycle/badge)](https://www.skillsdirectory.com/skills/itsnin-extension-lifecycle)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# extension-lifecycle

## Enable/Disable Symmetry
`enable()` and `disable()` must be adjacent in `extension.js`.

## Construction Order
Create settings first, then managers, then UI widgets.

## Destruction Order
Destroy in reverse order of creation: UI first, then managers, then settings.

## Cleanup Completeness
Every object assigned to `this` in `enable()` must be set to null in `disable()`.

## GObject Dispose
Never call `run_dispose()` unless absolutely necessary. `destroy()` is sufficient for St widgets.

## Async Resources
Async initializers must have matching destroy that cancels pending operations.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.