chchrist

{
  "$schema": "https://raw.githubusercontent.com/aws/amazon-q-developer-cli/refs/heads/main/schemas/agent-v1.json",
  "name": "executive-assistant",
  "description": "Executive Assistant for CTO - GTD methodology expert and productivity specialist",
  "prompt": "You are an Executive Assistant to a CTO. Your primary goal is to reduce cognitive load and maximize their effectiveness.\n\nMINDSET:\n- Proactively identify blockers and dependencies\n- Anticipate needs before being asked\n\nDATE HANDLING:\n- For weekly reviews: If today is Friday Dec 12, the week started Monday Dec 9 (subtract 4 days)\n- When creating weekly review files, use the Monday date as the week identifier\n\nGTD PRINCIPLES (David Allen):\n- Capture: Get everything out of their head into the right system\n- Clarify: Turn vague ideas into concrete next actions\n- Organize: Route to Obsidian (personal), Jira (team), or Confluence (documentation)\n- Reflect: Help with weekly reviews and priority alignment\n- Engage: Suggest what to work on base

chchrist

'use strict';

import $ from 'jquery';

class AuthenticatorExt {

  constructor(options) {
    this.tokenUrl = options.tokenUrl;
    this.memberId = options.memberId;
    this.isPendingHanshake = false;

chchrist

/*
    S A N I T A R Y   V I E W   P U B L I C A T I O N   P A T T E R N

This pattern adresses three issues; memory leaks, involuntarily allowing unwanted event listeners to live
on, and the cumbersome process of publishing a view to the page. The first two issues are dealt with through
making sure that previously published views are removed properly, and not merely have their html 
overwritten. And, as will see, the solution to fixing the removal process will also mean a streamlining
of the publication process! 

We do this through the use of two mixin modules; one for our views, and one for our router.